DNSMasq domain will not work, everything else works well

[JoQ]

Hi,

I have setup about 10 different adresses in my DNSMasq (AC68U).
Here's the list:
address=/bt.lan/cloud.lan/ftp.lan/home.lan/mov.lan/tv.lan/jackett.lan/media.lan/omv.lan/vpn.lan/vpn-admin.lan/plex.lan/web.lan/web2.lan/web3.lan/192.168.1.2

Everything works very well, except for one of the domain-names, "tv.lan".
If I try to reach this adress I get err_connection_timed_out.
And if I change my reverse proxy to "mov.lan" I reach this without any problems at all. Every other domain work with this service, but not tv.lan.

Is there any reason?
I would like to be able to use it.

 

[thelonelycoder]

If you do this through /jffs/configs/dnsmasq.conf.add you could simply add this for all *.lan domains to resolve to 192.168.1.2:

address=/lan/192.168.1.2

 

[thelonelycoder]

Also, before you change anything, did you check where the domain tv.lan resolves to?

ping tv.lan
and/or
tracert tv.lan
for Windows, for *NIX use: 
traceroute tv.lan

 

[JoQ]

Also, before you change anything, did you check where the domain tv.lan resolves to?

ping tv.lan
and/or
tracert tv.lan
for Windows, for *NIX use:
traceroute tv.lan

Just tried it, this is the result:

C:\Users\User>ping tv.lan

Pinging tv.lan [192.168.1.4] with 32 bytes of data:
Reply from 192.168.1.2: Destination host unreachable.
Reply from 192.168.1.2: Destination host unreachable.
Reply from 192.168.1.2: Destination host unreachable.
Reply from 192.168.1.2: Destination host unreachable.

Ping statistics for 192.168.1.4:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\User>tracert tv.lan

Tracing route to tv.lan [192.168.1.4]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  172.27.232.1
  2  NAS.lan [192.168.1.2]  reports: Destination host unreachable.

Trace complete.

To compare with bt.lan which works perfectly as all the others:

C:\Users\User>ping bt.lan

Pinging bt.lan [192.168.1.2] with 32 bytes of data:
Reply from 192.168.1.2: bytes=32 time=2ms TTL=64
Reply from 192.168.1.2: bytes=32 time=2ms TTL=64
Reply from 192.168.1.2: bytes=32 time=2ms TTL=64
Reply from 192.168.1.2: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 2ms, Average = 2ms

C:\Users\User>tracert bt.lan

Tracing route to bt.lan [192.168.1.2]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  NAS.lan [192.168.1.2]

Trace complete.

Btw, this was done while I was on VPN, but same issue when I am at home.
Looks like tv.lan points to 192.168.1.4, I have no idea why?

Thank you for your help!

 

[JoQ]

Solved it! My Samsung TV was named TV and has the IP 192.168.1.4
Renamed it and now tv.lan is free and working again!