Purpose of domain name under Wired Networks -> LAN -> Networks -> Interface settings?
If you go to the Settings tab and select "Wired Networks -> LAN" and then edit one of the networks, there's a section where it (optionally) asks for a Domain Name. The SDN manual does not explain what setting this value accomplishes. Does anyone know what the purpose of this field is for?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
If you set a domain as LAN in this section, you can use the domain not an IP to access the device which obtained the IP from the interface.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Right, I also set mDNS for all the VLANS
- Copy Link
- Report Inappropriate Content
I think this works as a search domain.
For example, if you enter yourdomain[dot]com in the domain field this will get passed down to the clients.
I you then try to ping PC1 from the client it will automatically convert this to PC1[dot]yourdomain[dot]com, the DNS record still has to exist on the DNS server.
- Copy Link
- Report Inappropriate Content
First of all I had to replace the dots in the addresses with something else as this forum keeps rejecting my post, doh!
Having fun with DNS LOL...
- Router LAN and VLANs have domain set to lan•example•com
- Router LAN and VLANs have DNS records pointing to my NAS (192•168•10•2)
- I even named clients on Omada, for example Camera for a given MAC address but I doubt it's for anything else but the display in Omada
- Named the device, for example EAP for my access point device in Omada
- Cloudflare DNS for example•com to my WAN
- On Cloudflare, set a CNAME *•example•com
- I have a reverse proxy on my NAS
- My local DNS server (on my NAS) have a zone for lan•example•com
- I also added a *•lan•example•com A record in my local DNS to point to my NAS for the reverse proxy to do its job
Now, on a PC
- I see that it's having a Connection-specific DNS Suffix with value lan•example•com coming from the router I believe (IPConfig /all)
- I can ping a server from the reverse proxy, for example test•lan•example•com
- Pinging eap•lan•example•com resolves to my NAS, probably because of the NAS DNS rule *•lan•example•com and not to the named device on omada
- Same for pinging EAP, resolve to my NAS as eap•lan•example•com
- Pinging another PC by name or FQDM gets resolved by the NAS proxy 😕
- Going with NSLOOKUP, now we enter strange lands
- DNS server is recognized as what I entered in Omada for the VLAN: 192•168•10•2 (my NAS)
- Querying for:
- MyPCName gives MyPCName•lan•example•com 192•168•10•2 (my NAS) 😕
- MyPCName•lan•example•com gives MyPCName•lan•example•com•lan•example•com 192•168•10•2 (My NAS) 🤪
- test gives test•lan•example•com 👍
- Any entries from the NAS DNS gives the address it is configured to 👍
- test•lan•example•com gives test•lan•example•com•lan•example•com 🤪
- google•com gives google•com•lan•example•com 🤪
Surely I have configured something wrong but out of ideas for solving this
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 1550
Replies: 8