PTR not showing in dig request
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
I am trying to set up a PTR
for reverse DNS so that mail that gets sent from me scripts doesn't get blocked due to reverse DNS failure. I beleive my zone is set up correctly, however me "thinking" it's correct and "knowing" it's correct are 2 seperate things!
First, I have: mydomain.com
This domain lives on public IP: 1.2.3.4
My conf
file in the bind
configuration looks like:
zone "mydomain.com"
type master;
file "/var/lib/bind/mydomain.com.hosts";
;
zone "4.3.2.1.in-addr.arpa"
type master;
file "/var/lib/bind/mydomain.com.reverse.hosts";
;
The mydomain.com.reverse.hosts file contains:
$ttl 38400
@ IN SOA ns1.mydomain.com. zak.mydomain.com. (
1502115400
10800
3600
604800
38400 )
IN NS ns1.mydomain.com.
IN NS ns2.mydomain.com.
4.3.2.1.in-addr.arpa. 3600 IN PTR mydomain.com.
Forward lookups work great -- IE dig mydomain.com A
and dig mydomain.com NS
both bring up the respective (correct) A and NS records. The reverse lookup however isn't showing the PTR
. IE:
zak@zak-webserver:~$ dig -x 1.2.3.4 PTR
; <<>> DiG 9.10.3-P4-Ubuntu <<>> -x 1.2.3.4
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1796
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;4.3.2.1.in-addr.arpa. IN PTR
Is my PTR record set up correctly? If so what are some checks I can do to find the failure point?
bind dns-zone reverse-dns
add a comment |Â
up vote
3
down vote
favorite
I am trying to set up a PTR
for reverse DNS so that mail that gets sent from me scripts doesn't get blocked due to reverse DNS failure. I beleive my zone is set up correctly, however me "thinking" it's correct and "knowing" it's correct are 2 seperate things!
First, I have: mydomain.com
This domain lives on public IP: 1.2.3.4
My conf
file in the bind
configuration looks like:
zone "mydomain.com"
type master;
file "/var/lib/bind/mydomain.com.hosts";
;
zone "4.3.2.1.in-addr.arpa"
type master;
file "/var/lib/bind/mydomain.com.reverse.hosts";
;
The mydomain.com.reverse.hosts file contains:
$ttl 38400
@ IN SOA ns1.mydomain.com. zak.mydomain.com. (
1502115400
10800
3600
604800
38400 )
IN NS ns1.mydomain.com.
IN NS ns2.mydomain.com.
4.3.2.1.in-addr.arpa. 3600 IN PTR mydomain.com.
Forward lookups work great -- IE dig mydomain.com A
and dig mydomain.com NS
both bring up the respective (correct) A and NS records. The reverse lookup however isn't showing the PTR
. IE:
zak@zak-webserver:~$ dig -x 1.2.3.4 PTR
; <<>> DiG 9.10.3-P4-Ubuntu <<>> -x 1.2.3.4
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1796
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;4.3.2.1.in-addr.arpa. IN PTR
Is my PTR record set up correctly? If so what are some checks I can do to find the failure point?
bind dns-zone reverse-dns
Do you manage the name servers for the reverse lookup DNS zone? My guess is no. The entity that manages the reverse lookup DNS zone (most likely your ISP) needs to create the PTR records.
â joeqwerty
2 hours ago
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I am trying to set up a PTR
for reverse DNS so that mail that gets sent from me scripts doesn't get blocked due to reverse DNS failure. I beleive my zone is set up correctly, however me "thinking" it's correct and "knowing" it's correct are 2 seperate things!
First, I have: mydomain.com
This domain lives on public IP: 1.2.3.4
My conf
file in the bind
configuration looks like:
zone "mydomain.com"
type master;
file "/var/lib/bind/mydomain.com.hosts";
;
zone "4.3.2.1.in-addr.arpa"
type master;
file "/var/lib/bind/mydomain.com.reverse.hosts";
;
The mydomain.com.reverse.hosts file contains:
$ttl 38400
@ IN SOA ns1.mydomain.com. zak.mydomain.com. (
1502115400
10800
3600
604800
38400 )
IN NS ns1.mydomain.com.
IN NS ns2.mydomain.com.
4.3.2.1.in-addr.arpa. 3600 IN PTR mydomain.com.
Forward lookups work great -- IE dig mydomain.com A
and dig mydomain.com NS
both bring up the respective (correct) A and NS records. The reverse lookup however isn't showing the PTR
. IE:
zak@zak-webserver:~$ dig -x 1.2.3.4 PTR
; <<>> DiG 9.10.3-P4-Ubuntu <<>> -x 1.2.3.4
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1796
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;4.3.2.1.in-addr.arpa. IN PTR
Is my PTR record set up correctly? If so what are some checks I can do to find the failure point?
bind dns-zone reverse-dns
I am trying to set up a PTR
for reverse DNS so that mail that gets sent from me scripts doesn't get blocked due to reverse DNS failure. I beleive my zone is set up correctly, however me "thinking" it's correct and "knowing" it's correct are 2 seperate things!
First, I have: mydomain.com
This domain lives on public IP: 1.2.3.4
My conf
file in the bind
configuration looks like:
zone "mydomain.com"
type master;
file "/var/lib/bind/mydomain.com.hosts";
;
zone "4.3.2.1.in-addr.arpa"
type master;
file "/var/lib/bind/mydomain.com.reverse.hosts";
;
The mydomain.com.reverse.hosts file contains:
$ttl 38400
@ IN SOA ns1.mydomain.com. zak.mydomain.com. (
1502115400
10800
3600
604800
38400 )
IN NS ns1.mydomain.com.
IN NS ns2.mydomain.com.
4.3.2.1.in-addr.arpa. 3600 IN PTR mydomain.com.
Forward lookups work great -- IE dig mydomain.com A
and dig mydomain.com NS
both bring up the respective (correct) A and NS records. The reverse lookup however isn't showing the PTR
. IE:
zak@zak-webserver:~$ dig -x 1.2.3.4 PTR
; <<>> DiG 9.10.3-P4-Ubuntu <<>> -x 1.2.3.4
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1796
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;4.3.2.1.in-addr.arpa. IN PTR
Is my PTR record set up correctly? If so what are some checks I can do to find the failure point?
bind dns-zone reverse-dns
bind dns-zone reverse-dns
asked 2 hours ago
Zak
1819
1819
Do you manage the name servers for the reverse lookup DNS zone? My guess is no. The entity that manages the reverse lookup DNS zone (most likely your ISP) needs to create the PTR records.
â joeqwerty
2 hours ago
add a comment |Â
Do you manage the name servers for the reverse lookup DNS zone? My guess is no. The entity that manages the reverse lookup DNS zone (most likely your ISP) needs to create the PTR records.
â joeqwerty
2 hours ago
Do you manage the name servers for the reverse lookup DNS zone? My guess is no. The entity that manages the reverse lookup DNS zone (most likely your ISP) needs to create the PTR records.
â joeqwerty
2 hours ago
Do you manage the name servers for the reverse lookup DNS zone? My guess is no. The entity that manages the reverse lookup DNS zone (most likely your ISP) needs to create the PTR records.
â joeqwerty
2 hours ago
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
Your PTR record seems fine, you can verify that by running dig
against your own DNS server.
However that doesn't mean much as long as a DNS resolution starting at the root dosn't ultimately arrive at your DNS server.
Normally you have to ask the ISP that assigned your IP address to set up a PTR record for that address.
This isn't on an ISP .. It's with a cloud-based host company .. I own the DNS server (dedicated) and the web server as well -- Are you saying that I need to contact my cloud provider and do this on an ISP level?
â Zak
2 hours ago
Then the cloud-based host company has/is an ISP. They should have a process to set PTR records for their addresses. Your own DNS server alone doesn't mean anything. I also have my own DNS server. If I set a PTR for that address, what makes your DNS server better than mine?
â RalfFriedl
1 hour ago
Ahh Great point! So one last question, should I remove that record as to not conflict with their record should they create it for me?
â Zak
1 hour ago
Yes, you should remove that record as it has no effect.
â RalfFriedl
1 hour ago
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
Your PTR record seems fine, you can verify that by running dig
against your own DNS server.
However that doesn't mean much as long as a DNS resolution starting at the root dosn't ultimately arrive at your DNS server.
Normally you have to ask the ISP that assigned your IP address to set up a PTR record for that address.
This isn't on an ISP .. It's with a cloud-based host company .. I own the DNS server (dedicated) and the web server as well -- Are you saying that I need to contact my cloud provider and do this on an ISP level?
â Zak
2 hours ago
Then the cloud-based host company has/is an ISP. They should have a process to set PTR records for their addresses. Your own DNS server alone doesn't mean anything. I also have my own DNS server. If I set a PTR for that address, what makes your DNS server better than mine?
â RalfFriedl
1 hour ago
Ahh Great point! So one last question, should I remove that record as to not conflict with their record should they create it for me?
â Zak
1 hour ago
Yes, you should remove that record as it has no effect.
â RalfFriedl
1 hour ago
add a comment |Â
up vote
3
down vote
accepted
Your PTR record seems fine, you can verify that by running dig
against your own DNS server.
However that doesn't mean much as long as a DNS resolution starting at the root dosn't ultimately arrive at your DNS server.
Normally you have to ask the ISP that assigned your IP address to set up a PTR record for that address.
This isn't on an ISP .. It's with a cloud-based host company .. I own the DNS server (dedicated) and the web server as well -- Are you saying that I need to contact my cloud provider and do this on an ISP level?
â Zak
2 hours ago
Then the cloud-based host company has/is an ISP. They should have a process to set PTR records for their addresses. Your own DNS server alone doesn't mean anything. I also have my own DNS server. If I set a PTR for that address, what makes your DNS server better than mine?
â RalfFriedl
1 hour ago
Ahh Great point! So one last question, should I remove that record as to not conflict with their record should they create it for me?
â Zak
1 hour ago
Yes, you should remove that record as it has no effect.
â RalfFriedl
1 hour ago
add a comment |Â
up vote
3
down vote
accepted
up vote
3
down vote
accepted
Your PTR record seems fine, you can verify that by running dig
against your own DNS server.
However that doesn't mean much as long as a DNS resolution starting at the root dosn't ultimately arrive at your DNS server.
Normally you have to ask the ISP that assigned your IP address to set up a PTR record for that address.
Your PTR record seems fine, you can verify that by running dig
against your own DNS server.
However that doesn't mean much as long as a DNS resolution starting at the root dosn't ultimately arrive at your DNS server.
Normally you have to ask the ISP that assigned your IP address to set up a PTR record for that address.
answered 2 hours ago
RalfFriedl
2,3111312
2,3111312
This isn't on an ISP .. It's with a cloud-based host company .. I own the DNS server (dedicated) and the web server as well -- Are you saying that I need to contact my cloud provider and do this on an ISP level?
â Zak
2 hours ago
Then the cloud-based host company has/is an ISP. They should have a process to set PTR records for their addresses. Your own DNS server alone doesn't mean anything. I also have my own DNS server. If I set a PTR for that address, what makes your DNS server better than mine?
â RalfFriedl
1 hour ago
Ahh Great point! So one last question, should I remove that record as to not conflict with their record should they create it for me?
â Zak
1 hour ago
Yes, you should remove that record as it has no effect.
â RalfFriedl
1 hour ago
add a comment |Â
This isn't on an ISP .. It's with a cloud-based host company .. I own the DNS server (dedicated) and the web server as well -- Are you saying that I need to contact my cloud provider and do this on an ISP level?
â Zak
2 hours ago
Then the cloud-based host company has/is an ISP. They should have a process to set PTR records for their addresses. Your own DNS server alone doesn't mean anything. I also have my own DNS server. If I set a PTR for that address, what makes your DNS server better than mine?
â RalfFriedl
1 hour ago
Ahh Great point! So one last question, should I remove that record as to not conflict with their record should they create it for me?
â Zak
1 hour ago
Yes, you should remove that record as it has no effect.
â RalfFriedl
1 hour ago
This isn't on an ISP .. It's with a cloud-based host company .. I own the DNS server (dedicated) and the web server as well -- Are you saying that I need to contact my cloud provider and do this on an ISP level?
â Zak
2 hours ago
This isn't on an ISP .. It's with a cloud-based host company .. I own the DNS server (dedicated) and the web server as well -- Are you saying that I need to contact my cloud provider and do this on an ISP level?
â Zak
2 hours ago
Then the cloud-based host company has/is an ISP. They should have a process to set PTR records for their addresses. Your own DNS server alone doesn't mean anything. I also have my own DNS server. If I set a PTR for that address, what makes your DNS server better than mine?
â RalfFriedl
1 hour ago
Then the cloud-based host company has/is an ISP. They should have a process to set PTR records for their addresses. Your own DNS server alone doesn't mean anything. I also have my own DNS server. If I set a PTR for that address, what makes your DNS server better than mine?
â RalfFriedl
1 hour ago
Ahh Great point! So one last question, should I remove that record as to not conflict with their record should they create it for me?
â Zak
1 hour ago
Ahh Great point! So one last question, should I remove that record as to not conflict with their record should they create it for me?
â Zak
1 hour ago
Yes, you should remove that record as it has no effect.
â RalfFriedl
1 hour ago
Yes, you should remove that record as it has no effect.
â RalfFriedl
1 hour ago
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f937419%2fptr-not-showing-in-dig-request%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Do you manage the name servers for the reverse lookup DNS zone? My guess is no. The entity that manages the reverse lookup DNS zone (most likely your ISP) needs to create the PTR records.
â joeqwerty
2 hours ago