how to check if my dns host setup is propogated

In my godaddy user portal  I can create alternative namservers

eg: nameserver1.mydomain.com       134.119.177.XXX
      nameserver2.mydomain.com       134.119.177.XXX

But how can I be sure that these namerservers are propogated and functioning?

Please note  that I am NOT asking for DNS lookup (like https://mxtoolbox.com/dnscheck.aspx)

Thank you
LVL 1
myyisAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MaheshArchitectCommented:
propagation and functioning are two different things

for propagation check, you need to use nslookup or mxtoolbox

but as far as functioning, it is depends on ISP, how he had configured DNS server, if this is standard ISP, then they should work as expected as long as one can reach up to them on their IP interface

The basic test you can carry is to telnet those both server hostnames / IP address from internet on TCP 53 (DNS port) , the test should be successful.
0
myyisAuthor Commented:
Thank you Mahesh,

I have tried the test, nameserver1.mydomain.com  does not function, let's say that's the problem of ISP.

But even it does not function after I follow the steps here  https://www.godaddy.com/help/add-my-own-host-names-as-nameservers-12320
nameserver1.mydomain.com  should propogate. Am I write?

If I am wrong  and for propogation nameserver1.mydomain.com  should function, how can it function before the setup and propogation I made in godaddy?
0
MaheshArchitectCommented:
here there are two problems:

if you cannot telnet nameserver1.domain.com, there are two possibilities:
either FQDN is not propagated and not able to resolve to correct IP address
OR
you are able to resolve server FQDN, in that case name resolution is working fine as propagation is done but ISP did not open up TCP 53 from internet on that server

You need to identify exact problem:
try telnet to DNS server IP instead of FQDN, if it works, then try to telnet same server on his FQDN, if it did not work it means propagation is not completed yet
when your telnet is working on both IP and FQDN, it means server is accepting DNS connections and queries
Later on you need to think on if server is able to resolve internet names quickly as expected, it depends upon how ISP configured DNS server
0
Challenges in Government Cyber Security

Has cyber security been a challenge in your government organization? Are you looking to improve your government's network security? Learn more about how to improve your government organization's security by viewing our on-demand webinar!

myyisAuthor Commented:
I use this tool to check
https://www.infobyip.com/tcpportchecker.php
When I test the ip address for  53 port it connects, when I test  nameserver1.mydomain.com it fails.
So is this a propogation problem? I think it is not because I have added nameserver1.mydomain.com to godaddy portal 1 week ago.
0
MaheshArchitectCommented:
is there host (A) record and NS records both available in go daddy panel for above DNS servers?, otherwise it will fail..
ns1.domain.com should have corresponding host(A) record pointing to public IP and same time it should have NS record as well pointing to ns1.domain.com
so when you query name server by FQDN, it should resolve to ns1.domain.com and ns1.domain.com intern will resolve to public IP
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
myyisAuthor Commented:
Godaddy has the domain control.
In godaddy mydomain.com is pointed  to NS3517.HOSTGATOR.COM right now.
What I am trying to make is move mydomain.com from hostgator shared to pivps vps. But pivps does not provide nameservers. So first I have to create a nameserver of my own (nameserver1.mydomain.com), register it on pivps vps  service  and then use nameserver1.mydomain.com instead of  NS3517.HOSTGATOR.COM
Right now I  do not have any DNS records on hostgator related with pivps vps
0
myyisAuthor Commented:
Let's say I have created  A and NS records on hostgator. And mynameserver started working. The next think I will do is I will point mydomain.com to mynameserver and close the account on hostgator. So the records on hostgator will not exist anymore. Then what should I do?
0
myyisAuthor Commented:
I decided to use the godaddys nameservers, thank you
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.