2
2
I have a set of virtual machines that I have to configure for a school assignment. I configured a DHCP and a DNS server at my server machine. At the DHCP file the option-domain-name servers
is pointing to the IP address of my DNS server and option-domain-name
has the name of my 'aulas' domain.
The thing is...I have another machine on my network with two interfaces. One of them is configured by my school DHCP server and the other interface is configured by my DHCP server (which works fine). For some reason when I make DNS requests with dig, the DNS query goes to the school DNS server, which (of course) will not know this 'aulas' domain and will return no answers. I'll put the link to my conf files here.
I know that if I edit the client file /etc/resolv.conf
and place my nameserver first it will solve the query. But if the two interfaces are both up and running the file will automatically be updated and will look like this:
nameserver 192.168.x.x
nameserver 10.0.0.1
search students.x.x.x.x aulas.asr
Here, the query goes to the first nameserver (school DNS) and returns no answers without even trying the second nameserver. If I remove the first nameserver it works like a charm for my aulas.asr domain. Do I need to make some sort of routing to use both interfaces at the same time? If so, how can I do it?
your PC is using the NIC that connects to your school as the default interface. What happens when you disable it and then try again? – xR34P3Rx – 2016-12-26T18:11:49.150
what you can also do is modify your ip address settings on the school NIC and manually set it to use your VM's IP. – xR34P3Rx – 2016-12-26T18:12:37.393