Why some site use different IP address for NS & A records
for e.g
NS1 IP is 100.x.x.1 which is pointed ns1.site.com
NS2 IP is 100.x.x.2 which is pointed ns2.site.com
++++++++++++++++++++++++++++
list of top cheapest hosting http://listtop.pw/
Top 200 best traffic exchange sites http://listtop.pw/surf
list of top gpt sites
list of top ptc sites
list of top ptp sites
list of top crypto currency Wallets sites
Listtop.pw
Listtop.pw
Listtop.pw
+++++++++++++++++++++++++++++
A IP 130.x.x.x
when ping & tracert the site it pings,tracert only A records IP not the NS IP why such a difference is there any advantage
note:
the site is not pointed to cloudflare NS
Why some site use different IP address for NS & A records
for e.g
NS1 IP is 100.x.x.1 which is pointed ns1.site.com
NS2 IP is 100.x.x.2 which is pointed ns2.site.com
A IP 130.x.x.x
when ping & tracert the site it pings,tracert only A records IP not the NS IP why such a difference is there any advantage
note:
the site is not pointed to cloudflare NS
Normally two name-servers are required for DNS redundancy.
That means, if one name-server is down from the IP range 100.x.x.1, your website DNS is still served from the totally different IP range 100.x.x.2.
if you use one IP for both the name-servers, in this case, if the IP network is down, your website will be down as well on the internet.
A DNS report for any of your domain can reveal this information:
Name-servers are on different IP subnets :-
Oops! One or more of your name-servers are on the same class C subnet. RFC2182 section 3.1 states that all of your name-servers should be in geographically and topologically dispersed locations for redundancy purposes.
While normally, different "A" record setup for your domain helps in overcoming blacklisting of mail server at major networks as the PTR over the "A" record is different.
just a though..
Warm regards
L3Web Hosting - Web hosting services at your fingertips
L3Tech Support - Support round the clock
If an IP doesn't ping it either means the firewall is blocking the iCMP packets or the IP isn't bound (setup) on the server. Check the IPs are actually bound. Also on the server it where those IPs are, try pinging local to that server to see if it pings there.
Also best practices state to have the nameservers on different ranges and in different geographic location.
-Steven | u2-web@Cooini, LLC - Business Shared Hosting | Isolate sites with Webspaces | Site Builder | PHP-FPM | MariaDB
WHMCS Modules: Staff Knowledgebase | Custom Modules and Hooks
"It is the mark of an educated mind to be able to entertain a thought without accepting it" -Aristotle
trafficspells.com
spacetreksurf.com
exabytes.sg
domain and range
bitplastic.com
startcryptogame.com
viralinbox.com
www.gsm hosting forum.com
hosting free
www.tecommandpost.com
thunderalleyte.com
hosting tips
domain 2 and 3
