Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 221
  • Last Modified:

Folder Domain Found Under Domain When Adding 'A' Host Record.

I'm having an issue entering an A record to my DNS server. Now the DNS server IS working and resolving names but this one little issue has me wondering what its doing.

Lets call this domain DOMAIN.COM

In the DOMAIN.COM folder in NT4 DNS Manager I click NEW RECORD and enter a new 'A' record for the name of this DNS server. We will call it NS.

Now when I go back to DNS manager and look at the 'A' record inside DOMAIN.COM I do notice it in there, BUT -- I also notice a FOLDER under the DOMAIN.COM. It looks like it made a sub-domain under DOMAIN.COM called NS.

On this DNS Server called NS, I have the following configuration set. On TCP/IP Properties on the DNS TAB I have:
 
HOST NAME: NS
DOMAIN:    DOMAIN.COM
DOMAIN SUFFIX SEARCH ORDER:   DOMAIN.COM

If I delete the FOLDER NS, then the name record for NS inside DOMAIN.COM also disappears. I re-enter the 'A' record again for NS and the folder returns. However I did add an 'A' record inside DOMAIN.COM for my secondary DNS server of NS2 and that did not make a directory, it worked fine.

Perhaps I'm doing something wrong or over looking something else.
0
T.J.
Asked:
T.J.
  • 2
1 Solution
 
arminlCommented:
Tried to do this to my NT 4 (SP6) DNS server, even used your name "company.com" --> no luck. I get a nice A record like expected, and no subdomains. The behaviour you describe seems like the DNS server thinks you want to delegate a subdomain. So I guess that you have somehow selected the NS record type instead of the A record type. To make sure: delete the old NS entry, and then use the "new host" menu instead of the "new entry" menu if you wish to create an A record.

Armin Linder
0
 
T.J.Author Commented:
Well I tried deleting the zone, but as soon as I tried to recreate it, it automatically brought all the same records back in, including the sub domain!

I guess maybe I should have stopped the DNS service and physically remove the zone file from the primary and secondary?
0
 
arminlCommented:
This sounds like you got a problem with the zone file. If you just delete and re-create a domain, and choose the same filename like before (domain.com.dns for example) DNS will reuse the old (corrupt?) zonefile and not create an empty one.

While conducting the following, I would net stop DNS on the secondary server and leave it down until tests have revealed any result.

Then I'd net stop DNS on the primary, go to c:\winnt\system32\dns and make a backup copy and then delete all .dns files, then restart the dns server.

Try to recreate the zone, does it work now?

If yes: stop DNS again, and bring back the old cache.DNS file. You will very likely need it, because it contains the root hint entries.

Restart your DNS. If the problem is back again: you can look into all .dns files, including cache.dns, they are just plain text. Cache.dns is the same on every DNS server, so you can copy an intact file from anywhere, or reinstall the DNS service to get a valid one.

Then bring back the secondary server.

Armin Linder
0
 
CleanupPingCommented:
ITGL72:
This old question needs to be finalized -- accept an answer, split points, or get a refund.  For information on your options, please click here-> http:/help/closing.jsp#1 
EXPERTS:
Post your closing recommendations!  No comment means you don't care.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now