![]() |
![]() |
#1 |
Junior Member
Join Date: Sep 2021
Posts: 4
|
![]()
Hello, your status page at [url]https://www.ventrilo.com/status.php[/url] does not appear to support SRV records. In contrast, Instant Ventrilo's does at [url]https://www.ventrilo4.com/ventrilo-server-status.php[/url].
A few people still use your status script and would like it to also resolve SRV records for servers like Instant Ventrilo's script. |
![]() |
![]() |
![]() |
#2 |
Administrator
Join Date: May 2005
Location: Some insignifcant planet.
Posts: 8,059
|
![]()
It works for here.
If you enter ventrilo.com with no port it will take you to the SRV record version of the server. |
![]() |
![]() |
![]() |
#3 |
Administrator
Join Date: May 2005
Location: Some insignifcant planet.
Posts: 8,059
|
![]()
Confirmed. Your example is having a problem. Will look at the problem closer to find out whats going wrong.
|
![]() |
![]() |
![]() |
#4 |
Junior Member
Join Date: Sep 2021
Posts: 4
|
![]()
I might have an idea, the SRV record is configured to return an IP address as this is what was desired. Whatever function handles understanding the return of that field in Ventrilo itself (probably a built in Windows function,) and the Lightspeed script likely is able to interpret this and just understands to connect to an IP address.
Your script I believe pulls it from the SRV record, and attempts a literal resolve of the address (which will fail, DNS servers do not return A records for an IP address, the IP address IS the A record,) and as a result, fails to "resolve it." Solutions would be to either change the function which "resolves this" so that it is more robust or flexible, or to check and see if the SRV record returns an IP and not to do a lookup on it. I don't suppose you guys are hiring for any form of programming work by chance? |
![]() |
![]() |
![]() |
#5 |
Administrator
Join Date: May 2005
Location: Some insignifcant planet.
Posts: 8,059
|
![]()
Found the problem. The front end of our status page is looking for a FQDN to exit, but the back end does not care, nor does the client (which was fixed a few years ago). This is problem on our side and I will fix as soon as possible.
At the current time all your domain has is an SOA record. However, you can fix this immediately if you provide an actual DNS A record for the domain. You might need to also provide a CNAME record for the "va" subdomain. This is a temporary solution until I apply the proper patch to our websites front end. FYI. Flag |
![]() |
![]() |
![]() |
#6 |
Junior Member
Join Date: Sep 2021
Posts: 4
|
![]()
I'll have to wait for the patch, I'm only allowed to administrate a SRV record for this domain, no A records nor CNAME records.
Thanks for looking into this. |
![]() |
![]() |
![]() |
#7 |
Administrator
Join Date: May 2005
Location: Some insignifcant planet.
Posts: 8,059
|
![]()
I'll try to make some time this weekend to fix it.
|
![]() |
![]() |
![]() |
#8 |
Administrator
Join Date: May 2005
Location: Some insignifcant planet.
Posts: 8,059
|
![]()
Fixed
|
![]() |
![]() |
![]() |
#9 |
Junior Member
Join Date: Sep 2021
Posts: 4
|
![]()
It appears to work just fine, thanks for looking into this.
|
![]() |
![]() |
![]() |
Thread Tools | |
Display Modes | |
|
|