Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Glue Record Questions
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Glue Record Questions

I have set the Glue Record on my registrar. How do I know the Glue Record has been "Glued". Where can I check it ?

«1

Comments

  • Is your domain resolving, now?

  • @Janevski said:
    Is your domain resolving, now?

    Can I ping to the Main Domain, Yes. Can I ping to the Glueed Records, No

  • WSSWSS Member

    Did you also add the A records to your zone?

    Thanked by 1Janevski
  • You can dig +trace, or use something like https://intodns.com to get insight.

  • @WSS said:
    Did you also add the A records to your zone?

    Is it really necessary to do that for the Glue Records to work ?

    I am using cloudflare as the nameserver of my main domain.

  • Check it here:
    https://intodns.com

  • What should I put there ? because it only support for domain not subdomain.

    I want to know whether my nsx.mydomain.com is finished gluing or not.

    @3606202 said:
    Check it here:
    https://intodns.com

  • WSSWSS Member

    @yokowasis said:

    @WSS said:
    Did you also add the A records to your zone?

    Is it really necessary to do that for the Glue Records to work ?

    I am using cloudflare as the nameserver of my main domain.

    I generally consider it good form; I've never tried to use it only as a glue record, as I manage my own nameservers.

    Try getting further information with dig.

    dig +trace +additional myzone.com - this should give you info what/where the nameservers it see are, et al..

  • yokowasisyokowasis Member
    edited July 2017

    What should I put on myzone.com ?

    mydomain.com or ns1.mydomain.com ?

    p.s. mydomain.com use cloudflare as the nameserver if that matter

    @WSS said:

    @yokowasis said:

    @WSS said:
    Did you also add the A records to your zone?

    Is it really necessary to do that for the Glue Records to work ?

    I am using cloudflare as the nameserver of my main domain.

    I generally consider it good form; I've never tried to use it only as a glue record, as I manage my own nameservers.

    Try getting further information with dig.

    dig +trace +additional myzone.com - this should give you info what/where the nameservers it see are, et al..

  • WSSWSS Member

    I'm afraid now is the time to do some reading.

    Thanked by 2Janevski vimalware
  • yokowasisyokowasis Member
    edited July 2017

    @WSS said:
    I'm afraid now is the time to do some reading.

    Any reference ? Because I tried googling how to check Glue Record, I found no definite answer.

  • yokowasisyokowasis Member
    edited July 2017

    Here is what I have so far :

    1. My main domain (example.com), using cloudflare nameserver. Obviously it works and able to resolve.

    2. Add a bunch of Glue Record to my registrar (ns1.example.com, ns2.example.com, ns3.example.com, etc). Won't resolve unless I add A record on my main domain cloudflare (of course with grey cloud).

    Hence the question, how can I check ns1.example.com already online and available to use? This is my first time adding a Glue Record, I just want to know whether

    • I add it right or,
    • my registrar has malfunction panel or
    • It still on propagation period.
  • bump. any help is appreciated.

  • WSSWSS Member

    If you only have a glue record, but you still use your own nameservers, it's not going to work until you add an A record, as you are SOA for that.

  • yokowasisyokowasis Member
    edited July 2017

    @WSS said:
    If you only have a glue record, but you still use your own nameservers, it's not going to work until you add an A record, as you are SOA for that.

    I have added the a record. dig @localhost shows a record. For main domain, ns1 and ns2. But dig without @localhost have no answer. domain still unresolved. The domain is ppdb-online.web.id. leafdns said it can't find my nameservers.

  • PwnerPwner Member

    Give it some time to dry, otherwise it'll just fall apart.

    Thanked by 1switsys
  • WSSWSS Member

    @yokowasis said:

    @WSS said:
    If you only have a glue record, but you still use your own nameservers, it's not going to work until you add an A record, as you are SOA for that.

    I have added the a record. dig @localhost shows a record. For main domain, ns1 and ns2. But dig without @localhost have no answer. domain still unresolved. The domain is ppdb-online.web.id. leafdns said it can't find my nameservers.

    Then it sounds like your glue records haven't propigated. Do dig as I suggested above using your zone.. not on your nameserver/localhost for resolution.

  • busbrbusbr Member

    If it is a .com/.net, you can actually Whois it:

    Server Name: NS1.GOOGLE.COM
    IP Address: 216.239.32.10
    Registrar: MARKMONITOR INC.
    Whois Server: whois.markmonitor.com
    Referral URL: http://www.markmonitor.com

  • WSSWSS Member

    @busbr said:
    If it is a .com/.net, you can actually Whois it:

    Server Name: NS1.GOOGLE.COM
    IP Address: 216.239.32.10
    Registrar: MARKMONITOR INC.
    Whois Server: whois.markmonitor.com
    Referral URL: http://www.markmonitor.com

    That won't necessarily show his zone IPs if he doesn't dig.. just the names.

  • What DNS software are you using? Is port 53 open? Make sure you have A records set for ns1 and ns2 pointing to your IP. Also don't forget to create IN records pointing to ns1.yourdomain and ns2.yourdomain.

  • yokowasisyokowasis Member
    edited July 2017

    @Saragoldfarb said:
    What DNS software are you using?

    BIND

    Is port 53 open?

    Yes, it is Open

    Make sure you have A records set for ns1 and ns2 pointing to your IP.

    Yes, it is pointing to my IP.

    Also don't forget to create IN records pointing to ns1.yourdomain and ns2.yourdomain.

    What is IN Record ? can you elaborate more ?

    Dig @localhsot result

    https://pastebin.com/yp901dqg

    Dig +trace +additional

    https://pastebin.com/797m8wmM

  • @WSS said:

    @yokowasis said:

    @WSS said:
    If you only have a glue record, but you still use your own nameservers, it's not going to work until you add an A record, as you are SOA for that.

    I have added the a record. dig @localhost shows a record. For main domain, ns1 and ns2. But dig without @localhost have no answer. domain still unresolved. The domain is ppdb-online.web.id. leafdns said it can't find my nameservers.

    Then it sounds like your glue records haven't propigated. Do dig as I suggested above using your zone.. not on your nameserver/localhost for resolution.

    leafdns said it is glued

    I am pretty sure the problem is on my server.

  • WSSWSS Member

    See that "Unreachable" part? Fix that.

  • @WSS said:
    See that "Unreachable" part? Fix that.

    Yea, that's the million dollar question. Trying to fix that for days.

  • WSSWSS Member

    Bind bind to your outside interface and try connecting from outside. Better yet, replace it with nsd. It's the same config for zones, but a hell of a lot better.

  • [email protected] (OpenDNS):
    dig NS +noadditional +noquestion +nocomments +nocmd +nostats +trace ns1.ppdb-online.web.id. @208.67.222.222
    
    .           518400  IN  NS  a.root-servers.net.
    .           518400  IN  NS  b.root-servers.net.
    .           518400  IN  NS  c.root-servers.net.
    .           518400  IN  NS  d.root-servers.net.
    .           518400  IN  NS  e.root-servers.net.
    .           518400  IN  NS  f.root-servers.net.
    .           518400  IN  NS  g.root-servers.net.
    .           518400  IN  NS  h.root-servers.net.
    .           518400  IN  NS  i.root-servers.net.
    .           518400  IN  NS  j.root-servers.net.
    .           518400  IN  NS  k.root-servers.net.
    .           518400  IN  NS  l.root-servers.net.
    .           518400  IN  NS  m.root-servers.net.
    ;; Received 228 bytes from 208.67.222.222#53(208.67.222.222) in 21 ms
    
    id.         172800  IN  NS  a.dns.id.
    id.         172800  IN  NS  b.dns.id.
    id.         172800  IN  NS  c.dns.id.
    id.         172800  IN  NS  e.dns.id.
    id.         172800  IN  NS  sec3.apnic.net.
    ;; Received 300 bytes from 198.41.0.4#53(198.41.0.4) in 36 ms
    
    web.id.         43200   IN  NS  e.dns.id.
    web.id.         43200   IN  NS  d.dns.id.
    web.id.         43200   IN  NS  c.dns.id.
    web.id.         43200   IN  NS  b.dns.id.
    ;; Received 200 bytes from 202.12.28.140#53(202.12.28.140) in 167 ms
    
    ppdb-online.web.id. 43200   IN  NS  ns1.ppdb-online.web.id.
    ppdb-online.web.id. 43200   IN  NS  ns2.ppdb-online.web.id.
    /usr/bin/dig: couldn't get address for 'ns1.ppdb-online.web.id': no more
    
    Thanked by 1WSS
  • WSSWSS Member

    Your glue records ain't shit.

  • @WSS said:
    Your glue records ain't shit.

    In that case I should close this thread and open another one regarding why my nameservers not working.

    Thanks.

  • SaragoldfarbSaragoldfarb Member
    edited July 2017

    @yokowasis said:

    What is IN Record ? can you elaborate more ?

    Sorry, ment to say NS records. It has been a long day :) anyway. Looks like there's something up with your DNS server as you can resolve the domain @ localhost. Anything weird going on in your firewall?

    Edit: It's definitely your server as I can't get a result when trying to do the lookup using the IP address. On another note, you might want to run ns2 on a different IP/server.

  • SaragoldfarbSaragoldfarb Member
    edited July 2017

    Check the output of: nping --udp -p 53 youripaddress


    sara@beatrix:# nping --udp -p 53 139.99.xx.xx Starting Nping 0.6.47 ( http://nmap.org/nping ) at 2017-07-24 20:52 EDT
    SENT (0.0399s) UDP 85.204.xx.xx:53 > 139.99.xx.xx:53 ttl=64 id=2331 iplen=28
    SENT (1.0402s) UDP 85.204.xx.xx:53 > 139.99.xx.xx:53 ttl=64 id=2331 iplen=28
    SENT (2.0412s) UDP 85.204.xx.xx:53 > 139.99.xx.xx:53 ttl=64 id=2331 iplen=28
    SENT (3.0422s) UDP 85.204.xx.xx:53 > 139.99.xx.xx:53 ttl=64 id=2331 iplen=28
    SENT (4.0432s) UDP 85.204.xx.xx:53 > 139.99.xx.xx:53 ttl=64 id=2331 iplen=28 Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A
    Raw packets sent: 5 (140B) | Rcvd: 0 (0B) | Lost: 5 (100.00%)
    Nping done: 1 IP address pinged in 5.06 seconds

    Run something like this to fix the port issue:


    iptables -I INPUT 1 -p udp --dport 53 -j ACCEPT
Sign In or Register to comment.