2

Missing Glue Record

Hi there. I am trying to point my domain registered at names.co.uk to my private nameservers. However the process fails with a message from names.co.uk telling me "Required parameter missing. V024 Missing Glue record for server ns1.mydomain.co.uk".

Pretty sure I have the correct settings in names.co.uk control panel (as below) with both ns1 & ns2 subdomains registered to the new IP's via A record:

DNS Settings:

  • Add/Modify DNS Zone: mydomain.co.uk
    • A, CNAME, AAAA, TXT and NS records
    • 'Host Name' 'Type' 'Result'
      • ns1 A xx.xx.xx.11
      • ns2 A xx.xx.xx.22

Then added the name server addresses:

Change Nameservers:

  • Change Nameservers: mydomain.co.uk
    • Primary nameserver*
      • ns1.mydomain.co.uk
    • Secondary nameserver*
      • ns2.mydomain.co.uk

Domain/Service(s) : www.mydomain.co.uk

My dig produces:

dig mydomain.co.uk any @xx.xx.xx.11

; <<>> DiG 9.8.3-P1 <<>> mydomain.co.uk any @xx.xx.xx.11
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22440
;; flags: qr aa rd; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 3
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;mydomain.co.uk.        IN  ANY

;; ANSWER SECTION:
mydomain.co.uk. 14400   IN  TXT "v=spf1 +a +mx +ip4:xx.xx.xx.52 ~all"
mydomain.co.uk. 14400   IN  MX  0 mydomain.co.uk.
mydomain.co.uk. 86400   IN  SOA ns1.mydomain.co.uk. info.mydomain.co.uk. 2015061103 86400 7200 3600000 86400
mydomain.co.uk. 86400   IN  NS  ns1.mydomain.co.uk.
mydomain.co.uk. 86400   IN  NS  ns2.mydomain.co.uk.
mydomain.co.uk. 14400   IN  A   xx.xx.xx.11

;; ADDITIONAL SECTION:
mydomain.co.uk. 14400   IN  A   xx.xx.xx.11
ns1.mydomain.co.uk. 14400   IN  A   xx.xx.xx.11
ns2.mydomain.co.uk. 14400   IN  A   xx.xx.xx.22

;; Query time: 93 msec
;; SERVER: xx.xx.xx.11#53(xx.xx.xx.11)
;; WHEN: Sat Jun 13 10:38:40 2015
;; MSG SIZE  rcvd: 241
  • Have you tried pinging or tracerouting to your nameserver subdomains? – Steve Jun 14 '15 at 10:34
  • Thank you. No, I assumed I couldn't do that as due to the V024 error the link between name and IP has not been created yet and as such the old DNS settings are still pointing to the old nameserver – mactwixs Jun 14 '15 at 10:48
  • ping ns1.mydomain.co.uk ping: cannot resolve ns1.mydomain.co.uk: Unknown host ping ns2.mydomain.co.uk ping: cannot resolve ns2.mydomain.co.uk: Unknown host – mactwixs Jun 14 '15 at 10:51
  • 1
    Having been a webhost in a previous life, I highly recommend NOT running your own DNS servers unless your business model requires that you are a SOA for other domains. You do not want your own DNS records on your DNS servers without at least external backup. It leaves absolutely no room for error and it almost impossible to do otherwise. It is always always always wise to host your DNS records outside of your domain and not on your NS at least for for your SOA and primary records. – closetnoc Jun 14 '15 at 17:02
  • 100% agree with closetnoc. Don't run your own DNS servers unless you have to. Reliable DNS hosting is very cheap or even free. Many DNS registrars offer it as a free service with domain registration. Many hosting companies offer it as a free service with web hosting. You can pay pennies for it at hosts like Amazon Route 53. – Stephen Ostermiller May 4 '17 at 19:38
2

As Patrick says, you need your registrar to put a glue record in place with your nameserver subdomains and IP addresses. I've been running a split horizon network like this for many years with my own master and backup nameservers only exposed though IPv6 and external backup DNS servers providing IPv4/6, with transfers from the master nameserver. I had to ask my registrar to use only the IPv6 addresses specifically because the web interface doesn't allow for it.

This allowed the the use of a dynamic external IPv4 address and a routed IPv6 /48 subnet from an IPv6 tunnel broker.

1

The problem is that your nameservers are in-bailiwick of your domain name: since you want mydomain.co.uk to use ns1.mydomain.co.uk and ns2.mydomain.co.uk as nameservers, to prevent a DNS resolution loop, you need to have them as glue records on registry nameservers which means you need to register first these nameservers at the registry with their IP addresses, and only after that you will be able to use them for your domain name.

You need to do that through your registrar, you either ask him to do it for you or they provide some kind of interface for you to do it.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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