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

    Some DNS problems

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 3 Posters 2.6k Views
    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.
    • G
      golden3159
      last edited by

      Ok before I get started, I will readily admit im not an expert by any means but I am always willing to learn.  I installed PFSense as an experiment to pick up some new skills and i've gotten nearly everything working except for a few DNS problems.

      I think the root of my problems is in my Domain setup in the main page.  Domain and Hostname really confuse me in the way it works.  I understand in Windows, that the hostname is basically what its called, something easy to identify the computer with.  I simply put 'firewall' into it.  However, I have no idea what to put into domain.  I don't own any domains nor do I have a windows domain setup.  So I just put 'firewall.com' into it to get past setup.

      What further confuses me is that whenever I ping another host using its Microsoft "computer name", e.g. examplehost, it pings as "computername.firewall.com".

      So that leads me to my 2 problems.

      1.  Remote Desktop doesn't work by computer name anymore, I have to use the IP addresses.  However, mapped drives and ping still works (as described above)

      2.  I am trying to setup some settings in DNS forwader.  I have the following checked:

      Register DHCP leases in DNS forwarder - (I think this is causing the ".firewall.com" extension on the hostname, I initially enabled it because I thought it would fix my Remote Desktop Problem)

      Register DHCP static mappings in DNS forwarder - I have some static IP's set, so I also enabled this.

      So for example here is what im trying to setup.  What a LAN client types "router", they are taken to 192.168.0.1.  I leave the "hostname" part blank (I'm honestly not sure what to put in there) and type "router" into domain and 192.168.0.1 into IP address.

      I set all the others up in a similar fashion but no matter what I type, it always takes me back to my original domain, (firewall.com)

      If there's anything I need to clear up, please let me know.  In the end, im pretty sure it has something to do with my initial domain settings.  Thanks in advance!

      1 Reply Last reply Reply Quote 0
      • P
        Perry
        last edited by

        As hostname you could use firewall or pfsense.
        As domain you should use local or lan when you don't own a domain.
        Tick all 3 under services -> dns and then you can ping firewall.local or pfsense.lan
        http://en.wikipedia.org/wiki/Domain_name
        http://en.wikipedia.org/wiki/FQDN
        http://en.wikipedia.org/wiki/Hostname

        /Perry
        doc.pfsense.org

        1 Reply Last reply Reply Quote 0
        • G
          golden3159
          last edited by

          @Perry:

          As hostname you could use firewall or pfsense.
          As domain you should use local or lan when you don't own a domain.
          Tick all 3 under services -> dns and then you can ping firewall.local or pfsense.lan
          http://en.wikipedia.org/wiki/Domain_name
          http://en.wikipedia.org/wiki/FQDN
          http://en.wikipedia.org/wiki/Hostname

          Ahh ok thanks, I got the Remote Desktop and the other mappings understood now.

          Just wondering, is there any way to go by either hostnames or domains, rather than both?  For example 'media' instead of 'mediacenter.local but without having to make it media.com.  And also for connecting to computers using ping and RDP.

          1 Reply Last reply Reply Quote 0
          • GruensFroeschliG
            GruensFroeschli
            last edited by

            If you get an IP per DHCP your client will have the same DNS suffix.
            Usually if you try to ping just the first part withing the same "subdomain" it will work.

            ie: psymia.mine.nu is my domain.
            a server is called whitemage –> whitemage.psymia.mine.nu
            a client is called redmage --> redmage.psymia.mine.nu
            Now if i ping on redmage "whitemage" it will work.

            Alternatively you could enter your own names in the DNS-forwarder.
            some screenshots to clarify:
            @http://forum.pfsense.org/index.php/topic:

            http://forum.pfsense.org/index.php/topic,9440.msg53573.html#msg53573

            We do what we must, because we can.

            Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

            1 Reply Last reply Reply Quote 0
            • G
              golden3159
              last edited by

              @GruensFroeschli:

              If you get an IP per DHCP your client will have the same DNS suffix.
              Usually if you try to ping just the first part withing the same "subdomain" it will work.

              ie: psymia.mine.nu is my domain.
              a server is called whitemage –> whitemage.psymia.mine.nu
              a client is called redmage --> redmage.psymia.mine.nu
              Now if i ping on redmage "whitemage" it will work.

              Alternatively you could enter your own names in the DNS-forwarder.
              some screenshots to clarify:
              @http://forum.pfsense.org/index.php/topic:

              http://forum.pfsense.org/index.php/topic,9440.msg53573.html#msg53573

              Ah ok, thanks, before it wasn't working by only hostname but now it works.

              Now im off to learn about all these different VPN terms so I can try to setup a VPN next!  :o

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.