Sign up ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

In reference to this question, I've been working with skv to fix their glue records and I'm sort of wondering what I should be seeing. They've called DNSMadeEasy and got assistance creating the glue records.

Here's what I see when I query a TLD server:

dig +norec NS

; <<>> DiG 9.8.3-P1 <<>> +norec NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36825
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 12

;           IN  NS

;; AUTHORITY SECTION:        172800  IN  NS        172800  IN  NS

;; ADDITIONAL SECTION: 172800 IN  A 172800 IN  A 172800 IN  A 172800 IN  A 172800 IN  A 172800 IN  A 172800  IN  A 172800  IN  A 172800  IN  A 172800  IN  A 172800  IN  A 172800  IN  A

This seems to indicate that the glue records are in place.

However, if I perform a whois on, I don't see IP addresses next to the servers listed. I called Network Solutions to ask them and they said that information cannot be altered and indicated that the information would be added automatically?

The other thing is that when I don't receive an ADDITIONAL section when I dig NS.

Is it possible these items will get automatically updated as the changes propagates? Or is there more I need to do?

Thanks, all!

share|improve this question
Yell at NetSol louder. – Michael Hampton Jul 12 '13 at 21:34
So you're saying I should be able to make this change. Have you done it before with them? – tcv Jul 12 '13 at 21:37
Hell, even GoDaddy lets you fix your own glue records. For NetSol to not do it is ridiculous. – Michael Hampton Jul 12 '13 at 21:45
I think I got the answer I needed from NetSol. What about the fact that "dig NS" doesn't show the ADDITIONAL section? – tcv Jul 12 '13 at 22:57
@tcv That doesn't display glue; it came from the authoritative nameservers. – Andrew B Jul 12 '13 at 23:29

2 Answers 2

up vote 1 down vote accepted

By all appearances your glue is fine and the WHOIS database is running behind.

  • WHOIS databases are not necessarily up to date. What you're being told is that the nameserver information within WHOIS is automatically populated and you can't edit this. Since WHOIS is purely informative and not relied upon for any type of nameserver authority, this is acceptable.
  • dig <somedomain> NS does not display the glue that nameservers use to find a domain. As your dig output against the root nameservers shows, the glue is present. The DNS response that comes back with the missing additional records originates from the authoritative nameservers for, which can only be fixed by the parties who operate the nameservers.


$dig +norecurse NS

; <<>> DiG 9.7.3 <<>> +norecurse NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56608
;; flags: qr aa; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0

;                       IN      NS

;; ANSWER SECTION:                86400   IN      NS                86400   IN      NS                86400   IN      NS

;; Query time: 24 msec
;; WHEN: Fri Jul 12 19:43:33 2013
;; MSG SIZE  rcvd: 110

Keep in mind that the missing ADDITIONAL section is not strictly necessary: the minimal-responses option in BIND explicitly disables it in reply packets except in cases where required by RFC. (i.e. delegations)

share|improve this answer
Thanks, Andrew. I have a suspicion why the whois is not autopopulating, but do I need to make sure that information is there? – tcv Jul 13 '13 at 2:10
@tcv Nope. The nameserver data in WHOIS is for information purposes only and is not a part of the DNS spec at all. I honestly think the problem will go away if you ignore it for awhile. – Andrew B Jul 13 '13 at 6:32
Thanks again, Andrew. I've had to go through third and fourth parties to get all the done. The pace is out of my hands and slow so I'm frustrated. I want it all done. Thanks for your reassurances. – tcv Jul 13 '13 at 14:18


  1. Go to Network Solutions account page
  2. Log in to your Account Manager using your username and password
  3. Click on “My Products & Services” tab
  4. Select “My Domain Names”
  5. Scroll down to “More Domain Options” section and click on “Manage Name Servers” icon
  6. Input the primary nameserver you want to create and click “Go”
  7. You will need to enter the IP address for your new name server, once it is entered click “Go”.
  8. You will be asked to confirm and save the changes. Click “Save Changes” if you are satisfied with your entry.
  9. A confirmation screen will confirm that your changes have been saved.

Repeat to add secondary name server with your IP address.

share|improve this answer
I got as far as step 6. I think I'll need to get NetSol to address it. Sigh. – tcv Jul 12 '13 at 22:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.