I have changed name server of mypleaks.com like 24 hours back but it is still not updated.
It's still giving me below name servers which is old:-
Name Server: ns-****.awsdns-**.org
Name Server: ns-***.awsdns-**.com
Name Server: ns-****.awsdns-**.co.uk
Name Server: ns-***.awsdns-**.net
then tested it and got this result on zonemaster
where it's giving three Errors like below:-
No common nameserver IP addresses between child.
Parent has nameserver(s) not listed at the child
None of the nameservers listed at the parent are listed at the child.
Your question is offtopic as not related to programming.
You are in a lame delegation case, the list of nameservers do not match at the registry and in your own.
If you query the parent zone, you get now:
$ dig #a.gtld-servers.net mypleaks.com NS +noall +nodnssec +auth
; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> #a.gtld-servers.net mypleaks.com NS +noall +nodnssec +auth
; (2 servers found)
;; global options: +cmd
mypleaks.com. 172800 IN NS ns-107.awsdns-13.com.
mypleaks.com. 172800 IN NS ns-613.awsdns-12.net.
mypleaks.com. 172800 IN NS ns-1069.awsdns-05.org.
mypleaks.com. 172800 IN NS ns-1710.awsdns-21.co.uk.
But if you query these nameservers they do not believe to be authoritative on your domain:
;; ANSWER SECTION:
mypleaks.com. 300 IN NS ns1.digitalocean.com.
mypleaks.com. 300 IN NS ns2.digitalocean.com.
mypleaks.com. 300 IN NS ns3.digitalocean.com.
So you need to go back to Amazon and make the configuration needed so that all these 4 nameservers (or others as provided by Amazon) are indeed authoritative for your domain (in which case the second reply will be the same as the first, which is currently not the case).
Related
My objective is to setup site like noip/dyndns.
I have purchased domain ( say locations.com ). In my cpanel i have redirected that into a static ip (say 128.10.10.10)
I have created subdomain (say device.locations.com) and redirected it to a another static ip
(say 128.20.20.20). This is working fine.
How ever i wish to setup dynamic DNS service in device.locations.com (128.20.20.20)
I laredy installed bibd (version 9 in Centos 7)
Probluem is :
say I have a dynamic client. Which i registered as "serial001.device.locations.com" which is having ip ( 50.50.60.1 , which will change over the time)
if i issue "dig serial001.device.locations.com" in dns server (128.20.20.20/device.locations.com ) I'll get,
;; ANSWER SECTION:
serial001.device.locations.com. 10 IN A 50.50.60.1
However if i issue "dig serial001.device.locations.com" in other machine i am not getting any answer.
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52799
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
if i specifically say to use nameserver as above (i have pointed jayaruvandns.tk to 128.20.20.20)
dig #locationsdns.tk serial001.device.locations.com
;; ANSWER SECTION:
serial001.device.locations.com. 10 IN A 50.50.60.1
Can i know how can i fix this issue?
( I am really new to DNS )
I have followed below blog.
Original Post -Build your own DynDNS
My configuration was missing DNS record in my config file
You have to add these two DNS records to your example.com nameserver:
>dyn NS ns.example.com
>ns A 203.0.113.17
I transferred my domain ( simplifybits.com) using Route 53 and it successfully transferred.
However my domain is not resolving anymore :(
This is what my setup looks looks like
There are two buckets in S3
simplifybits.com
www.simplifybits.com
Route 53 configuration
simplifybits.com - A
s3-website.us-east-2.amazonaws.com.
simplifybits.com - NS
ns-1069.awsdns-05.org.
ns-31.awsdns-03.com.
ns-1556.awsdns-02.co.uk.
ns-535.awsdns-02.net.
simplifybits.com - SOA
ns-1069.awsdns-05.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
www.simplifybits.com - A
d3v4utl52t4eyk.cloudfront.net.
I had this same problem. Right now your domains still have Google as the name servers:
Tech Email: tech#simplifybits.com.whoisprivacyservice.org
Name Server: ns-cloud-d1.googledomains.com
Name Server: ns-cloud-d2.googledomains.com
Name Server: ns-cloud-d3.googledomains.com
Name Server: ns-cloud-d4.googledomains.com
It isn't obvious but go to the "Hosted zones" tab and select your domain. Then, copy the "NS" records. Now go to the "Registered domains" and select your domain. If you look you will likely see to the right that the "Name servers" still have Google. Click on "Add or edit name servers" and enter your name servers from above. The popup will keep adding lines for you.
It took me a while to get this right as, like you, I thought I had to only have the NS records correct but that isn't enough.
As #steve-harris points out you will still have to have S3 enabled to serve static content but you'll want to get DNS going first.
I've migrated one domain to Route 53. The migration was successful, but NS of domain points to NS of previous registrar. I've tried to change the values to new NS generated for HostedZone, but the operation is still stuck. In the dashboard I can see:
domainname.it --- Name server update in progress --- 2016-12-16
18:47:41
After 4 days it's always in "in progress" state.
When I try to change it again, I've got this message:
"You can't edit NS because you have an pending request"
Amazon do not provide any support for this issue. What can I do to resolve this problem?
It takes 6 days to unlock pending request. After that I was able to change NS in 2 minutes.
I have an internal domain, say example.com, in Windows AD DNS. I have created a sub-domain delegation, aws.example.com, with a glue record pointing to a BIND 9.8 instance in AWS (over site-to-site VPN).
The BIND instance has a single zone configured as a forward only (with forwarder) pointing to the AWS VPC subnet resolver which has an AWS Rt. 53 zone (aws.example.com) associated.
The problem is resolution is not functioning correctly, sometimes.... from my internal network if I dig or nslookup against the Windows DNS for hosts in the Rt. 53 zone, i get no answer (although I do see the query hitting BIND). If I then dig/nslookup against the BIND instance directly it works.
Now if I go back to the first step, dig/nslookup against Windows DNS, I do get successful resolution.
It's as if the initial dig/nslookup, which is coming via Windows DNS, isn't triggering the forward only behavior and the direct query is & then caching the answer.
Can anyone provide insight into what I've done wrong or how to change this behavior?
BIND config:
acl goodclients {
172.31.0.0/16;
192.168.0.0/16;
localhost;
localnets;
};
options {
directory "/var/cache/bind";
recursion yes;
allow-query { goodclients; };
forwarders {
172.31.0.2;
};
#forward only;
dnssec-enable yes;
dnssec-validation yes;
auth-nxdomain no; # conform to RFC1035
listen-on-v6 { any; };
querylog yes;
};
zone "aws.example.com" {
type forward;
forward only;
forwarders { 172.31.0.2; };
};
here's a sample of the fail-succeed-succeed sequence running queries to windows then bind then windows again from 2 different clients:
windows AD dns domain example.com
\_ subdomain aws.example.com —> NS 172.31.32.5 (bind instance in AWS )
\_ —> forwarding to:172.31.0.2 (aws VPC resolver IP) to Rt.53 associated zone
client 1:
user1#vfvps-server:~ #date
Wed Sep 14 14:18:41 EDT 2016
user1#vfvps-server:~ #nslookup
> lserver 192.168.4.147 <—————windows dns
Default server: 192.168.4.147
Address: 192.168.4.147#53
> server1.aws.example.com
Server: 192.168.4.147
Address: 192.168.4.147#53
** server can't find server1.aws.example.com: NXDOMAIN
> exit
client 2:
KWK-MAC:~ user1$ date
Wed Sep 14 14:19:29 EDT 2016
KWK-MAC:~ user1$ dig #172.31.32.5 server1.aws.example.com <—— 172.31.32.5 = bind
; <<>> DiG 9.8.3-P1 <<>> #172.31.32.5 server1.aws.example.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23154
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 0
;; QUESTION SECTION:
;server1.aws.example.com. IN A
;; ANSWER SECTION:
server1.aws.example.com. 300 IN A 172.31.14.41
client 1:
user1#vfvps-server:~ #date
Wed Sep 14 14:19:40 EDT 2016
user1#vfvps-server:~ #nslookup
> lserver 192.168.4.147
Default server: 192.168.4.147
Address: 192.168.4.147#53
> server1.aws.example.com
Server: 192.168.4.147
Address: 192.168.4.147#53
Non-authoritative answer:
Name: server1.aws.example.com
Address: 172.31.14.41
Windows DNS server configured with subdomain delegation will send iterative query to your BIND server. BIND will respond only if it is authoritative or from cache.
(you can try dig +norecurse server1.aws.example.com #172.31.32.5 and it will fail)
In your Windows DNS, you need to configure "Conditional Forwarder" for aws.example.com.
I have a site hosted on AWS and recently the site went down with NXDOMAIN error. The site was working before and the issue doesn't appear to be with the site as the Elastic Beanstalk direct link (xxxx-prod.elasticbeanstalk.com) is working fine.
In my Route53 I have a CNAME linking to my (xxxx-prod.elasticbeanstalk.com) and a SOA and 4 NS records supplied by AWS. xxxx is a placeholder for the actual site name. Running dig...
dig xxxx.com any
; <<>> DiG 9.8.3-P1 <<>> xxxx.com any
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63003
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;xxxx.com. IN ANY
;; AUTHORITY SECTION:
com. 895 IN SOA a.gtld-servers.net. nstld.verisign-grs.com. 1435723016 1800 900 604800 86400
;; Query time: 31 msec
;; SERVER: 64.71.255.204#53(64.71.255.204)
;; WHEN: Tue Jun 30 23:57:22 2015
;; MSG SIZE rcvd: 102
It looks like my NS records might be the issue but I am not sure. Can someone confirm.
TLDR: you need to contact your registar to figure out what's happening with the domains. You've left the domain in the question so I actually tried looking at what DNS was seeing for it.
Do you have an A record for your domain?
host vizibyl.com
Host vizibyl.com not found: 3(NXDOMAIN)
https://www.whois.net ->
Name Server: NS-1519.AWSDNS-61.ORG
Name Server: NS-1828.AWSDNS-36.CO.UK
Name Server: NS-228.AWSDNS-28.COM
Name Server: NS-544.AWSDNS-04.NET
Status: clientHold http://www.icann.org/epp#clientHold
Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
http://www.icann.org/epp#clientHold
for clientHold:
This status code tells your domain's registry to not activate your domain in the DNS and as a consequence, it will not resolve. It is an uncommon status that is usually enacted during legal disputes, non-payment, or when your domain is subject to deletion.
Often, this status indicates an issue with your domain that needs resolution. If so, you should contact your registrar to resolve the issue. If your domain does not have any issues, but you need it to resolve, you must first contact your registrar and request that they remove this status code.