• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Can ping & traceroute 'pfsense.mydomain.me' but can't access in browser as URL (times out)

ACME
3
23
6.8k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    johnpoz LAYER 8 Global Moderator @phantom99
    last edited by Mar 26, 2024, 3:58 PM

    @phantom99 and that screams your browser is not using your dns, ie its using doh.. Because clearly your OS just doing a query for that resomves it to the ip

    So from you cmd line on your os when you do a ping pfsense.home.arpa it comes back with that IP right.

    An intelligent man is sometimes forced to be drunk to spend time with his fools
    If you get confused: Listen to the Music Play
    Please don't Chat/PM me for help, unless mod related
    SG-4860 24.11 | Lab VMs 2.7.2, 24.11

    P 1 Reply Last reply Mar 27, 2024, 12:13 AM Reply Quote 0
    • P
      phantom99 @johnpoz
      last edited by Mar 27, 2024, 12:13 AM

      @johnpoz Yup.

      phantom@MAC-client ~ % ping pfsense.home.arpa
      PING pfsense.home.arpa (192.168.10.10): 56 data bytes
      64 bytes from 192.168.10.10: icmp_seq=0 ttl=64 time=0.431 ms
      64 bytes from 192.168.10.10: icmp_seq=1 ttl=64 time=0.580 ms

      And yet...
      Through DHCP: DNS server is set to LAN
      Search domain: home.arpa
      login-to-view

      ********** STOP PRESS ***************
      You have solved this!!

      OM*G - After a clean install, I somehow knew there was something basic at the heart of this. Of course it takes knowledge and expertise to narrow down on where the issue might lie.
      And that is what you have done.
      On top of that, you have had the patience and grace to stick this out and not fob me off, whilst undoubtedly doing the same for many others.
      I am most grateful.

      I now can access (firstly using hostname), and now also FQDN.
      Without security warnigns of course. ;)

      I suspect there was something else I had clutzed that started this entire thread....prior to the clean re-build , but again it was your help that guided me to the right place.

      After your definitive statement that it was Browser not using pfsense DNS, I found I could access using hostname on others browsers - Safari, Chrome, but had been using Brave. Somehwere down the line I suspect I had followed a tip on Privacy of DNS searches and changed Braves security/DNS settings to use OpenDNS. (Embarrassed. )

      For completeness I am posting the Brave setting.
      Thanks again, @johnpoz you are a legend and DNS God. <Nows, tips hat and swirls hand in a manner fit to introduce a King>

      login-to-view

      login-to-view

      Finally, I hope this is not considered a waste of your time. You have taught me quite a bit along the way

      J 1 Reply Last reply Mar 27, 2024, 1:26 AM Reply Quote 0
      • J
        johnpoz LAYER 8 Global Moderator @phantom99
        last edited by Mar 27, 2024, 1:26 AM

        @phantom99 just glad you got it sorted.. I could talk for hours and hours about dns ;)

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.7.2, 24.11

        1 Reply Last reply Reply Quote 1
        21 out of 23
        • First post
          21/23
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.