0

I have created my /etc/network/interfacesconfigured like this: /etc/network/interfaces

Then I have 2 files i created in /etc/bind One of them is db.rag.es , which looks like this: db.rag.es file

And the other one is db.222.168.192 which looks like this db.222.168.192 file

Problem is whenever I ping servidor.rag.esit returns a proper responde from (192.168.222.2), but if i ping ftp.rag.es for some reason it pings to 192.168.22.4(desired) , but then ive a destination host unreachable coming from 192.168.222.2when im trying to ping .4 ping attempt

mouchin777
  • 117
  • 5
  • What happens when you ping 192.168.222.4 (not using the name ftp.rag.es)? If you get no response then it is not a DNS problem. – Daniel K Nov 24 '19 at 17:51
  • @DanielK destination host unreachable, apparently not a dns problem then. Its returtning from 192.168.222.2 for some reason – mouchin777 Nov 24 '19 at 17:52
  • That is your NIC responding. This is normal. – Daniel K Nov 24 '19 at 18:08
  • @DanielK thanks for the clues, solved it by modifying /etc/network/interfaces by following this https://wiki.debian.org/NetworkConfiguration#Multiple_IP_addresses_on_one_Interface – mouchin777 Nov 24 '19 at 19:18
  • Do not use `ping` to troubleshoot DNS issues, it is the wrong tool (for almost any troubleshooting in fact). DNS issues are to be troubleshoot using `dig` or a least `nslookup`. Also when asking for help remember to put all relevant information (which could be in your case DNS server configuration and zone content) IN the question (not through a remote link that can become stale) and AS TEXT (to enable copy, search, etc.). Do not bother first with reverse DNS also until you understand how this space is delegated (completely separate from domain names). You have online DNS troubleshooting sites – Patrick Mevzek Nov 25 '19 at 17:53

1 Answers1

1

This is not a DNS problem. It is likely a firewall issue.

davidgo
  • 5,964
  • 2
  • 21
  • 38
  • I have no firewall in my machine – mouchin777 Nov 24 '19 at 17:39
  • In that case its a routing issue. What does your network look like? (Ie how are systems connected, what are the netmasks and routes?) – davidgo Nov 24 '19 at 17:43
  • its a virtualbox virtualmachine running ubuntu, with the posted network configuration to have a static ipv4. Internal adapter is connected to "Internal network" – mouchin777 Nov 24 '19 at 17:47
  • solved it by following https://wiki.debian.org/NetworkConfiguration#Multiple_IP_addresses_on_one_Interface to add extra ip addresses – mouchin777 Nov 24 '19 at 19:19
  • This is not an answer. It could be any number of things preventing communication, including the firewall – Daniel K Nov 24 '19 at 21:15
  • 1
    @DanielK - The point is that it is not a DNS problem, which is what the OP thought and the best answer available wit the given information (and enough to put the OP on the correct path it seems) – davidgo Nov 24 '19 at 22:11