Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 4 subscribers
  • Views 5479 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to configure one DNS hostname for a host with two NICs?

Jas Man

Hi,


I've a host with a LAN and a WiFi NIC. In the past I had configured one static DHCP IP address with a single hostname for both adapters/MAC addresses. But every time, when I switched immediatly from WiFi to LAN or vice versa, the new connection didn't get this static IP address. I think the UTM said then "Sorry dude, this IP is already in use. Please come back later...".

So I made two static DHCP reservations, one for the LAN and one for the WiFi NIC. But now I can only confiugre one reservation with the FQDN of the host. When I try to configure the second reservation with the same FQDN the UTM says "Already in use".

Is the only way to configure such a scenario with two different FQDNs like "Host-LAN.jasnet.intern" and "Host-WIFI.jasnet.intern"? What is best practise?

Thanks!

Jas



This thread was automatically locked due to age.
Parents
  • 0

    The way I got around this was to create a network definition for my hosts that contains a common name for the object, a specific DNS host name that matches the machine FQDN and add an alias in the advanced section.  I also put in my MAC addresses and make them static DHCP reservations while I'm at it.  This way I can have one common FQDN for the host, but the UTM will understand its alias and multiple MAC addresses.  The only part I'm not sure about for you is that if you want both NIC's online at the same time it would basically be a round robin response from DNS when you try to resolve the host name.  

  • 0 in reply to JoeChurch

    Hi Joe,

    Thank you for your answer.

    That's exactly what I did. But when I switch from LAN to WiFi or vice versa, the new connection gets no IP address. I've to reboot or wait until it works. Maybe it's a problem of the client. Could you confirm that this works ASAP when you switch between the NICs?

    Jas

Reply
  • 0 in reply to JoeChurch

    Hi Joe,

    Thank you for your answer.

    That's exactly what I did. But when I switch from LAN to WiFi or vice versa, the new connection gets no IP address. I've to reboot or wait until it works. Maybe it's a problem of the client. Could you confirm that this works ASAP when you switch between the NICs?

    Jas

Children
No Data
Unfiltered HTML