Thread: Name Resolution

    #1
  1. No Profile Picture
    Junior Member
    Devshed Newbie (0 - 499 posts)

    Join Date
    Dec 2001
    Location
    PA, but I'm interested in moving
    Posts
    2
    Rep Power
    0

    Unhappy Name Resolution


    I recently set up a Win2kServer to host the website in-house. I'm able to pull up the website with the IP address, but I can't seem to figure out how to get the domain name resolved through DNS. Just a couple days ago, I registered our static IP as NS1.domain.com at the registrar, then listed it as the primary name server. But it seems to me that I still don't have something configured quite right.
  2. #2
  3. No Profile Picture
    Contributing User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jan 2001
    Posts
    4
    Rep Power
    0
    >> I can't seem to figure out how to get the domain name resolved through DNS

    You need to run an authoritative DNS server.

    >> then listed it as the primary name server

    So what, you still need to run an authoritataive DNS server at the IP.
  4. #3
  5. No Profile Picture
    Junior Member
    Devshed Newbie (0 - 499 posts)

    Join Date
    Dec 2001
    Location
    PA, but I'm interested in moving
    Posts
    2
    Rep Power
    0

    Authoritative DNS


    Thanks freebsd for your input on this, I've been researching this without any success for a couple months...

    I found a white paper about making a DNS server authoritative on the Win2KServer: "A DNS server is considered authoritative for a name if it loads the zone containing that name. The first record in any zone file is a Start of Authority (SOA) RR. The SOA RR identifies a primary DNS name server for the zone as the best source of information for the data within that zone and as an entity processing the updates for the zone."

    I have server.domain.com listed under Forward Lookup Zones of the DNS server, and in Properties of server.domain.com SOA the Primary server is listed as server.domain.com. which is a FQDN. Which seems to satisfy that, but I may be wrong. Am I missing something?

    (I don't know if this has anything to do with it, but the Serial number in the Properties SOA has been incremented to 38. Whereas I have a fwd.domain.com Forward Lookup Zone that has a Serial number of 1.)
  6. #4
  7. No Profile Picture
    Contributing User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jan 2001
    Posts
    4
    Rep Power
    0
    I can't help you with DNS configuration in M$. In UNIX, the serial is for slave authoritative DNS server to compare it with the master. Other than SOA, you also need NS and A at the minimum.

    >> I registered our static IP as NS1.domain.com

    NS for domain.com should be pointed to ns1.domain.com. Your SOA should point to ns1.domain.com as well. In addition, you need to set an A record, that's to point ns1.domain.com to your static IP. For your other FQDNs like server.domain.com and fwd.domain.com just need A record and point them to the same IP. If you need to setup MX, set domain.com to point to ns1.domain.com (not mail.domain.com).

IMN logo majestic logo threadwatch logo seochat tools logo