VPN no longer works only with Second-Level Domain

Issue #296 invalid
XL created an issue

Hiii Maintainers,

So I have recently updated my R6400v1 to 2023.4 version.

Coincidentally I found out that my old way of using VPN policies stopped working.

So I was using only Second-Level Domain like google instead of google.com, it worked like a charm.

After this update, it stopped working somehow.
Now I have to enter the whole domain to make it working.

So is it a Bug?

Idk if it’s just me or everyone is like that…

Comments (3)

  1. pedro repo owner

    I don't know what you did before, but it never worked as you describe because, among other things, it uses nslookup:

    root@router:/tmp/home/root# nslookup google
    Server:    127.0.0.1
    Address 1: 127.0.0.1 localhost
    
    nslookup: can't resolve 'google'
    root@router:/tmp/home/root# nslookup google.com
    Server:    127.0.0.1
    Address 1: 127.0.0.1 localhost
    
    Name:      google.com
    Address 1: 2a00:1450:4014:80f::200e prg03s13-in-x0e.1e100.net
    Address 2: 142.251.36.110 prg03s11-in-f14.1e100.net
    

    So you have to input the whole domain:

    Type -> To Domain - Ex: "domain.com". Please enter one domain per line

  2. XL reporter

    Dear pedro,

    thanks for your response.

    I might have remembered it wrong.

    Yet I have tested it with only TLD, it works though. Like .cc or .io (but not with the period)

    since only using second level domains doesnt work, is there possible to use any kind of wildcard to input domain?
    For example xxxhub.com:
    I have tested *hub.com or with regex \S+hub.com, they dont work.

    The reason is some domains tend to have xxxhubwow.com as a neighbour domain, when accessing xxxhub.com, it will also be accessed.

  3. Log in to comment