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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Is your domain resolving, now?
Can I ping to the Main Domain, Yes. Can I ping to the Glueed Records, No
Did you also add the A records to your zone?
You can dig +trace, or use something like https://intodns.com to get insight.
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.
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..
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
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.
Here is what I have so far :
My main domain (example.com), using cloudflare nameserver. Obviously it works and able to resolve.
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
bump. any help is appreciated.
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.
Give it some time to dry, otherwise it'll just fall apart.
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.
If it is a .com/.net, you can actually Whois it:
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.
BIND
Yes, it is Open
Yes, it is pointing to my IP.
What is IN Record ? can you elaborate more ?
Dig @localhsot result
https://pastebin.com/yp901dqg
Dig +trace +additional
https://pastebin.com/797m8wmM
leafdns said it is glued
I am pretty sure the problem is on my server.
See that "Unreachable" part? Fix that.
Yea, that's the million dollar question. Trying to fix that for days.
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.
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.
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.
Check the output of: nping --udp -p 53 youripaddress
Run something like this to fix the port issue: