Can not resolve a DNS

johnpoz

So doesn't look like your getting any answer from the NS for that domain.

melita.com. 172800 IN NS ns.melitacable.com.
melita.com. 172800 IN NS ns1.melitacable.com.

Query them directly!!

Their IPs I gave ealier, but here they are again.
ns1.melitacable.com. 86088 IN A 212.56.128.196
ns.melitacable.com. 86088 IN A 212.56.128.132

so from pfsense

drill @212.56.128.196 melita.com


[2.3.2-RELEASE][root@pfsense.local.lan]/root: drill @212.56.128.196 melita.com
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 58179
;; flags: qr aa rd ; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;; melita.com.  IN      A

;; ANSWER SECTION:
melita.com.     86400   IN      A       212.56.128.204

;; AUTHORITY SECTION:
melita.com.     86400   IN      NS      ns1.melitacable.com.
melita.com.     86400   IN      NS      ns.melitacable.com.

;; ADDITIONAL SECTION:
ns.melitacable.com.     86400   IN      A       212.56.128.132
ns1.melitacable.com.    86400   IN      A       212.56.128.196

;; Query time: 157 msec
;; SERVER: 212.56.128.196
;; WHEN: Mon Nov 28 15:17:58 2016
;; MSG SIZE  rcvd: 123


[2.3.2-RELEASE][root@pfsense.local.lan]/root: drill @212.56.128.132 melita.com
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 30011
;; flags: qr aa rd ; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;; melita.com.  IN      A

;; ANSWER SECTION:
melita.com.     86400   IN      A       212.56.128.204

;; AUTHORITY SECTION:
melita.com.     86400   IN      NS      ns1.melitacable.com.
melita.com.     86400   IN      NS      ns.melitacable.com.

;; ADDITIONAL SECTION:
ns.melitacable.com.     86400   IN      A       212.56.128.132
ns1.melitacable.com.    86400   IN      A       212.56.128.196

;; Query time: 158 msec
;; SERVER: 212.56.128.132
;; WHEN: Mon Nov 28 15:18:55 2016
;; MSG SIZE  rcvd: 123
[2.3.2-RELEASE][root@pfsense.local.lan]/root:

Chrismallia

;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 0
;; flags: ; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; . IN NS

;; ANSWER SECTION:

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 0 msec
;; WHEN: Mon Nov 28 22:28:30 2016
;; MSG SIZE rcvd: 0
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 0
;; flags: rd ; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; 4.36.112.192.in-addr.arpa. IN PTR

;; ANSWER SECTION:

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 0 msec
;; WHEN: Mon Nov 28 22:28:30 2016
;; MSG SIZE rcvd: 0
. 518400 IN NS d.root-servers.net.
. 518400 IN NS f.root-servers.net.
. 518400 IN NS j.root-servers.net.
. 518400 IN NS k.root-servers.net.
. 518400 IN NS e.root-servers.net.
. 518400 IN NS c.root-servers.net.
. 518400 IN NS g.root-servers.net.
. 518400 IN NS a.root-servers.net.
. 518400 IN NS h.root-servers.net.
. 518400 IN NS b.root-servers.net.
. 518400 IN NS m.root-servers.net.
. 518400 IN NS l.root-servers.net.
. 518400 IN NS i.root-servers.net.
;; Received 492 bytes from 192.112.36.4#53(G.ROOT-SERVERS.NET.) in 63 ms

;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 0
;; flags: ; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; 212.56.128.196. IN A

;; ANSWER SECTION:

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 0 msec
;; WHEN: Mon Nov 28 22:28:33 2016
;; MSG SIZE rcvd: 0
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 0
;; flags: ; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; 212.56.128.196. IN A

;; ANSWER SECTION:

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 0 msec
;; WHEN: Mon Nov 28 22:28:48 2016
;; MSG SIZE rcvd: 0
. 86400 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2016112801 1800 900 604800 86400
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 0
;; flags: rd ; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; 12.4.33.192.in-addr.arpa. IN PTR

;; ANSWER SECTION:

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 0 msec
;; WHEN: Mon Nov 28 22:28:48 2016
;; MSG SIZE rcvd: 0
;; Received 107 bytes from 192.33.4.12#53(c.root-servers.net.) in 58 ms

Chrismallia

;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 0
;; flags: ; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; . IN NS

;; ANSWER SECTION:

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 0 msec
;; WHEN: Mon Nov 28 22:31:41 2016
;; MSG SIZE rcvd: 0
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 0
;; flags: rd ; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; 4.36.112.192.in-addr.arpa. IN PTR

;; ANSWER SECTION:

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 0 msec
;; WHEN: Mon Nov 28 22:31:41 2016
;; MSG SIZE rcvd: 0
. 518400 IN NS b.root-servers.net.
. 518400 IN NS i.root-servers.net.
. 518400 IN NS a.root-servers.net.
. 518400 IN NS e.root-servers.net.
. 518400 IN NS m.root-servers.net.
. 518400 IN NS j.root-servers.net.
. 518400 IN NS l.root-servers.net.
. 518400 IN NS k.root-servers.net.
. 518400 IN NS h.root-servers.net.
. 518400 IN NS d.root-servers.net.
. 518400 IN NS g.root-servers.net.
. 518400 IN NS f.root-servers.net.
. 518400 IN NS c.root-servers.net.
;; Received 492 bytes from 192.112.36.4#53(G.ROOT-SERVERS.NET.) in 62 ms

;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 0
;; flags: ; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; 212.56.128.132. IN A

;; ANSWER SECTION:

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 0 msec
;; WHEN: Mon Nov 28 22:31:41 2016
;; MSG SIZE rcvd: 0
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 0
;; flags: ; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; 212.56.128.132. IN A

;; ANSWER SECTION:

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 0 msec
;; WHEN: Mon Nov 28 22:31:57 2016
;; MSG SIZE rcvd: 0
. 86400 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2016112801 1800 900 604800 86400
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 0
;; flags: rd ; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; 12.4.33.192.in-addr.arpa. IN PTR

;; ANSWER SECTION:

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 0 msec
;; WHEN: Mon Nov 28 22:31:57 2016
;; MSG SIZE rcvd: 0
;; Received 107 bytes from 192.33.4.12#53(c.root-servers.net.) in 56 ms

johnpoz

dude what are you doing???? If your going to paste something please paste the actual command you are running..

Those are not from the commands I gave you..

drill @212.56.128.132 melita.com

Chrismallia

Sorry but when I did drill @212.56.128.132 melita.com it comes up with nothing

johnpoz

comes up with nothing?? You mean you just get blank line??

Can you ping that IP

[2.3.2-RELEASE][root@pfsense.local.lan]/root: ping 212.56.128.132
PING 212.56.128.132 (212.56.128.132): 56 data bytes
64 bytes from 212.56.128.132: icmp_seq=0 ttl=54 time=158.707 ms
64 bytes from 212.56.128.132: icmp_seq=1 ttl=54 time=157.865 ms
64 bytes from 212.56.128.132: icmp_seq=2 ttl=54 time=156.402 ms
64 bytes from 212.56.128.132: icmp_seq=3 ttl=54 time=156.760 ms

what do you mean comes up with nothing?? Doesn't give you a failure doesn't give you a time out? Just nothing??

even if use some BS IP that doesn't answer dns.. you get something..

[2.3.2-RELEASE][root@pfsense.local.lan]/root: drill @212.56.1.1 melita.com
Error: error sending query: Could not send or receive, because of network error
[2.3.2-RELEASE][root@pfsense.local.lan]/root:

Chrismallia

It loads for a while then turn back this way

drill.png_thumb

johnpoz

Dude!!! Run the command from a shelll prompt please… SSH to pfsense!!!

doktornotor

hda

@johnpoz:

Dude!!!…

Goin' on for months now, I think you need to come to Malta :)
https://forum.pfsense.org/index.php?topic=107947.msg601506#msg601506

johnpoz

Yeah I thought this was a familiar domain ;) But I currently resolve it without any issue.. But can not seem to get the OP to post up stuff that validates he is having issues talking to the NS..

If I can reslove it from this side of the planet.. you would think he should not have any issues when he is on the same part of the planet as the NS ;)

But yeah info has been like teeth pulling with a pair of chopsticks..

@Chrismallia could you just give me remote access to your pfsense?? This would make it so much easier to figure out what the actual issue is.. Other than the domain in question has issues with their dns.. I just want to validate that you can not even talk to their NS..

hda

@johnpoz:

…But can not seem to get the OP to post up stuff that validates he is having issues talking to the NS..

Curious to know if @Chrismallia still uses the Malteser-ISP DNS-server anywhere in his pfSense config…
(and just not a clean use of the pfSense Resolver on 127.0.0.1).

johnpoz

I would be curious as well.. I am hoping he will just give me remote access and can put this to bed finally ;)

Chrismallia

doktornotor lool gled of being a entertainment looooll. As for dns. John sure I will give you access

dns.png_thumb

Chrismallia

John thank you soooo muchh you where Great ISP is trash hope to switch soon

johnpoz

So I got in via TV, and ssh Yeah for whatever reason he can not talk to the NS for that domain. Which is ODD since that is his ISP!!! The dns servers they hand out via dhcp are different then the NS for that domain.. He can talk to them just fine.. WTF??

So put him back in forwarder mode, so until he works it out with his ISP or changes - which he mentioned they looking at..

We can call this thread closed I would think.. Unless you have some questions Chrismallia.. Thanks for giving me remote access – made it so much faster to actually validate that you could not talk to them!!

Chrismallia

Hi John Thanks again goes to you for the great work. Yes this topic can be closed.

Thanks pfsense team