Recommended Posts

i have a website setup internally using apache. its website.met. my ip is 192.168.1.99 in the domain controller i made a new A record point website.met to 192.168.1.99 i flushed the dns on the client and the client cannot resolve the website. y does it not work?

one thing i can think of is the user's permission to the domain controller to resolve the dns!!

Well, the Web Server should be using it's full FQDN. So, if your domain was example.com then the Web Server should be something like webserver.example.com and you'd only need to setup a new a record for WebServer.

the domain is called mydomain.local so would i have to make a A record pointing at mydomain.local.website.met and then create a CNAME with that pointing to website.met ?

one thing i can think of is the user's permission to the domain controller to resolve the dns!!

no, thats not the case.

No, you'd make an A record called website.met.mydomain.local.

Your Domain Name goes after the Hostname of the Device. If you want to be able to hit 'Website.met' directly with no further intervention then you need to create a new forward lookup zone called .met and add website* to it.

No, you'd make an A record called website.met.mydomain.local.

Your Domain Name goes after the Hostname of the Device. If you want to be able to hit 'Website.met' directly with no further intervention then you need to create a new forward lookup zone called .met and add website* to it.

i made a A record and it automatically put mydomain.local to its right but I removed it and left it website.met but I think it made its own foward lookup zone..........

obviously i made a mistake but sadly im not the network admin so i cant be saying lets try this and that....

Well, your Network admin WILL know what he needs to do to setup something like this.

he doesnt. i just told him that i wanted to point website.met to my ip because i am running a web site with apache there and he told me that i would have to tell him how to do it as he does not know how to.

told him 2day and here it is....

Just make sure the hostname on your Linux box thats running the WebServer is setup correctly and has a Static IP.

it is a windows box and yes: it is static.

he doesnt. i just told him that i wanted to point website.met to my ip because i am running a web site with apache there and he told me that i would have to tell him how to do it as he does not know how to.

Then he shouldn't be a working in Networking - my partners 9 year old can already handle DNS configuration.

it is a windows box and yes: it is static.

If it's Windows, Bind to the Domain and it's instantly resolvable. Active Directory will automatically add the appropriate A Records.

Then he shouldn't be a working in Networking - my partners 9 year old can already handle DNS configuration.

go tell him (my boss) that........he didnt even know where to go in windows server to do it.

If it's Windows, Bind to the Domain and it's instantly resolvable. Active Directory will automatically add the appropriate A Records.

so therefore, I create a new A record and just leave the mydomian.local that is automatically appended to the right. ill try asking him to do tha if it doesnt work, then i guess ill just leave it alone.

You don't need to create anything, if the Windows Server that is running the Apache Server is joined to the domain as website.met then it'll automatically be resolvable.

?

i have apache server on pc 1 (my pc) dc is another pc, pc 2, i want the apache server to accessed by pc 3, 4, 5 (other pcs) on dc. all connected to dc.

it is not on ws/dc............

Okay

Domain name is mydomain.local

Domain Controller for example is called dc.mydomain.local

Apache Server is called website.met.mydomain.local

Other PCs are called PC1.mydomain.local, PC2.mydomain.local, PC3.mydomian.local etc

When website.met is joined to mydomain.local it gets the FQDN of website.met.mydomain.local

When a user types http://website.met into a Web Browser it'll search the network for a name containing website.met and then try the outside world. This is called a Search Domain, when it finds website.met.mydomain.local it'll automatically connect to the correct IP address and load the page.

Okay

Domain name is mydomain.local

Domain Controller for example is called dc.mydomain.local

Apache Server is called website.met.mydomain.local

Other PCs are called PC1.mydomain.local, PC2.mydomain.local, PC3.mydomian.local etc

When website.met is joined to mydomain.local it gets the FQDN of website.met.mydomain.local

When a user types http://website.met into a Web Browser it'll search the network for a name containing website.met and then try the outside world. This is called a Search Domain, when it finds website.met.mydomain.local it'll automatically connect to the correct IP address and load the page.

yes. exactly. the first five lines describe exactly the situation.

so how would i set that up on the dns server????

yes. exactly. the first five lines describe exactly the situation.

so how would i set that up on the dns server????

I think the answer of "You don't" is particular pertinent here.

As CPressland has stated, the fact that the Apache Web server (presumably running on a Windows box connected to the "domain" in question), the Domain's DC, and the clients actively looking to connect to the Apache Website will all be on the same domain, and connected accordingly, means you don't have to create a DNS record. As long as your Apache web server is called "website.met" you're all good!

Just make sure you are connected to the domain and as CPressland has stated, the DNS records will automatically be created on the DNS server

What is the name of the Apache server?

Start > Right Click Computer > Properties

PC1

all pcs here (except the dc) are named lik that with the number being the differece.

I think the answer of "You don't" is particular pertinent here.

As CPressland has stated, the fact that the Apache Web server (presumably running on a Windows box connected to the "domain" in question), the Domain's DC, and the clients actively looking to connect to the Apache Website will all be on the same domain, and connected accordingly, means you don't have to create a DNS record. As long as your Apache web server is called "website.met" you're all good!

Just make sure you are connected to the domain and as CPressland has stated, the DNS records will automatically be created on the DNS server

are you saying "it just works"? im sure id have to make a entry for this apache virutal hsot to be seeable by all....

"DNS records will automatically be created on the DNS server"

That is if the domain is not jacked up -- with a network admin that does not know how to create a A record, or where even to look for dns on the DC?

I am taking odds that prob not ;)

so you called your machine website.met ?? Really that is an odd name for a computer, could you post the output of hostname. And then just do a nslookup for the name that is output from hostname.

example

C:\Windows\System32>hostname

i5-w7

C:\Windows\System32>nslookup i5-w7

Server: pfsense.local.lan

Address: 192.168.1.253

Name: i5-w7.local.lan

Address: 192.168.1.100

C:\Windows\System32>

edit: Well if your computer is called PC1, then no its not just going to work.. You need to create the records in dns to point to the name you want for your website.

Do you have access to dns on the DC?

here

http://support.microsoft.com/kb/324260

How To Configure DNS Records for Your Web Site in Windows Server 2003

Same thing if 2k8 or 2k8r2, etc.. Send that link to your so called network admin

"DNS records will automatically be created on the DNS server"

That is if the domain is not jacked up -- with a network admin that does not know how to create a A record, or where even to look for dns on the DC?

I am taking odds that prob not ;)

so you called your machine website.met ?? Really that is an odd name for a computer, could you post the output of hostname. And then just do a nslookup for the name that is output from hostname.

example

C:\Windows\System32>hostname

i5-w7

C:\Windows\System32>nslookup i5-w7

Server: pfsense.local.lan

Address: 192.168.1.253

Name: i5-w7.local.lan

Address: 192.168.1.100

C:\Windows\System32>

edit: Well if your computer is called PC1, then no its not just going to work.. You need to create the records in dns to point to the name you want for your website.

Do you have access to dns on the DC?

here

http://support.microsoft.com/kb/324260

How To Configure DNS Records for Your Web Site in Windows Server 2003

Same thing if 2k8 or 2k8r2, etc.. Send that link to your so called network admin

no my machine is called PC1. the apache server has a virtual host called website.met the apache server is on PC1

here -- this is how you do it if you want to resolve website.met to your 192.168.1.99 address

post-14624-0-23822200-1337161780.jpg

See its a forward zone called met, with A record of website

I had to change what server I did my nslookup too, because I do not use that box as my dns

you could also do it with a cname pointing to your pc1.whaterdomainyourusing -- but lets just keep it REAL SIMPLE!!

Doesn't matter! Interface is the same, create a new primary forward zone called met, then A record of website.

Right click forward lookup zones, new zone, primary -- call it met

Then right click then new zone met and create A record website with your IP you want to point it too

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Go for a Echo Dot or Pop instead. These Echo shows just advertise to you.
    • NetSpeedTray 1.3.3 by Razvan Serea NetSpeedTray is a lightweight, open-source Windows network monitor that shows live upload and download speeds directly on the Taskbar. Designed for efficiency, it quietly sits in the system tray, conserving CPU and battery with dynamic updates. It blends seamlessly with Windows 10/11, adapts to light/dark themes, and auto-positions to avoid overlaps. Features include accurate interface detection, customizable display, optional mini-graph, color coding, granular font and unit control, detailed per-interface history graphs, safe data management, and easy CSV export—bringing the network monitoring Windows forgot. NetSpeedTray key features: Lightweight & Efficient Runs quietly in your system tray without consuming resources. Features a "Dynamic Update Rate" that lowers refresh frequency when the network is idle to save CPU and battery life. Native Look & Feel Blends seamlessly with Windows 10/11 UI. Smart detection for light and dark taskbar themes ensures text is always visible. Intelligent & Adaptive Positioning Automatically finds empty space next to your system tray and shifts to make room for new icons, preventing overlaps. Seamless OS Integration Behaves like a native Windows component. Hides instantly with auto-hiding taskbar Hides when a fullscreen app is active Smart Network Monitoring Accurate by Default: Auto mode identifies your main internet connection and ignores noise from VPNs or virtual adapters. Easy Interface Selection: Switch effortlessly between Auto, All, or Selected network interfaces via intuitive radio buttons. Total Visual Customization Free Move Mode: Unlock and place the widget anywhere on your screen. Optional Mini-Graph: Real-time graph of recent network activity with adjustable opacity. Color Coding: Customize colors and speed thresholds to quickly see network status. Granular Display Control Text & Font: Adjust font family, size, weight, and alignment. Units: Automatic (B/s, KB/s, MB/s) or fixed Mbps display. Precision: Set decimal places and always show them for uniform appearance. Detailed & Intelligent History Graph Smart Scale: Logarithmic scale shows low-level traffic and large spikes clearly. Per-Interface Filtering: View speed history for specific adapters (Wi-Fi, Ethernet, VPN). Safe & Efficient Data Management: Adjustable retention, automatic cleanup, optimized database. Easy Data Export: Export raw data to .csv or save high-quality graphs for reports. NetSpeedTray v1.3.3: The Updater Fix A stabilization release that repairs a critical regression in v1.3.2: the app shipped without OpenSSL, which silently broke every HTTPS request — including the built-in update checker (the "Could not check for updates" error many of you hit). This release restores it, hardens the build so it can't happen again, and fixes a startup crash plus four other reported bugs. Changes: Fixed update checking — Resolved a critical issue that prevented the app from checking for updates ("Could not check for updates"). Fixed startup crash with Auto-Cycling — The app no longer crashes on launch after enabling Cycle display mode. Fixed incorrect network speeds on 10GbE adapters — Multi-gigabit network cards now display speeds correctly instead of being stuck at 0. Improved color coding — Default color is shown when idle, and color/threshold changes now apply immediately without restarting. Fullscreen visibility fix — The widget now correctly stays visible over fullscreen apps when Keep Visible is enabled. Improved AMD Ryzen temperature detection — More reliable CPU temperature monitoring for Ryzen processors. Cleaner upgrades — Installer now removes outdated application files during upgrades, preventing DLL/version conflicts while preserving user settings. Improved stability — Fixed potential DLL loading issues by excluding critical OpenSSL and NumPy components from UPX compression. Better settings window — Scrollbars removed and layout improved for a cleaner experience. Localization improvements — Updated translations and completed missing UI text across all supported languages. More reliable releases — Added regression tests covering recent critical fixes, bringing the test suite to 196 passing tests. [full release notes] Download: NetSpeedTray 1.3.3 | 87.9 MB (Open Source) Download: NetSpeedTray Portable | 101.0 MB View: NetSpeedTray Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Why Delta Chat is the best decentralized messenger you have probably never tried by Paul Hill There is no shortage of messaging apps out there; we have WhatsApp, Messenger, and Telegram, just to name a few. While Meta has taken steps to incorporate encryption into Messenger and WhatsApp, they still leave a lot to be desired. If you are in the market for a messaging app that promotes security, privacy, and optional anonymity, you'll want to read what I have to say about Delta Chat. For those not familiar with Delta Chat, rather than relying on centralized servers as you do with Facebook Messenger, it relies on email. Essentially, it is a chat interface that feels like a messaging app, but secretly in the background, it is firing off emails. In the past, you used to have to sign in with your email account. When you sent messages to people, it would just be sending encrypted messages to their inbox, which their Delta Chat client would decrypt. When I first learned about Delta Chat, it required users to sign in with an email account, but I was pleasantly surprised upon trying it in 2026 that this is no longer a requirement, or the preferred method was to use the app. Recently, I’ve tried UAD-ng on my old Nokia 3.4 to disable most of the Google apps because the bootloader is locked, and this is the next best option. While finding replacement apps in F-Droid, I came across Delta Chat again, and it has undergone quite a big change since I last used it, with its new chatmail relays, which no longer require you to sign in to your own email account, providing anonymity, and they offer greater security. Android and Desktop Delta Chat apps. Not only does it run on my de-googled phone, but it also works on desktop computers and iOS, making it truly ubiquitous. For me, Delta Chat is a wonderful alternative messenger because it gives you more control. It supports switching between different profiles, which you can set up super quickly; you don’t register a username, you don’t register a password. The only thing you do have is a random string email address on a chatmail relay (which you don’t have to memorize). To maintain access to your profile, you just need to add a second device to your account via QR code or make a backup of your account, which you can restore later. Fail to do these, your account is gone - as it should be if you don’t want to leave accounts that could get hacked later on. My decision to block Google stuff on my Nokia was done for practical reasons; the device sucked when it launched, and it sucks even more now. The nice thing about F-Droid and the apps within is that they’re usually lightweight, free of bloat, and work well on that device. What was inconvenient for me was that it was hard to send messages from that device, say if I wanted to copy a code over to my main phone or send family members a link from that device. That’s when I decided to look at the available chat apps and saw Delta Chat. Another nice thing about Delta Chat is its notifications. Some messaging apps rely on Google’s ecosystem for notification transport on Android; however, with Delta Chat, it can use Google’s solutions if you have Play Services or MicroG installed. Otherwise, it is able to keep a background connection to the chatmail relay server so that you can get notified when you receive a message. As free software, the code of Delta Chat is open for all who want to take it and build upon it. In the future, if the developers of Delta Chat make a catastrophically bad decision and take the app in an undesirable direction, users can take the code and fork the project. This contrasts with closed-source apps from corporations that can take their products in any direction they like. By relying on free software instead of closed-source programs, you actually control your computing. I’ve spoken at length about how running this type of software is like owning your own home rather than renting it. The same applies here; if you use Delta Chat, you don’t need to worry about it going away in the future. Whether it is Telegram, WhatsApp, or Messenger, you are required to register a username and password to use these services. A major flaw in this design is that anyone can try various passwords and potentially break into your account with your complete chat history intact. Sure, there is encryption in Messenger, where you need a second PIN and two-factor authentication in Telegram, but breaches happen all the time. Unlike before, when you used to sign in to your email account to send and receive messages, the primary way to do it now is to create an account on a chatmail relay. The resulting email address is a random string followed by the name of the relay you pick. This means you can start and begin adding contacts Without a username and password, you either need to ensure you have a backup or at least one device running your Delta Chat profile. The primary way to log in on another device is to go to the settings and add a second device. Then, you’ll just scan a QR code with your new device, and it’ll log in to your account and sync all your chat history and contacts. To end users, Delta Chat just looks like any instant messenger; however, it is really sending your messages as encrypted emails to your contact. This is pretty cool from a censorship perspective, as it makes the service more difficult to block. Previously, the main way to use the app was by logging in with email, but nowadays, it’s recommended that you use chatmail relays. Chatmail relays temporarily hold messages in case your device is offline. They are cheap, simple servers that don’t store data as group states. Other information, like your name and avatar, only exists on your device and the devices of those you share your contact information with. The relays are also decentralized and operated by various groups and individuals. It is even possible to set up your own chatmail relay, but most people will want to use one hosted elsewhere. To keep your messages secure, Delta Chat uses a secure subset of the OpenPGP standard that gives you automatic end-to-end encryption. It also uses Secure-Join to exchange encryption setup information through QR-code scanning or invite links. Autocrypt is also used to automatically establish end-to-end encryption between contacts and all members of group chat, but sometime this year Autocrypt v2 will be rolled out, bringing post-quantum resistant encryption and forward secrecy. The Delta Chat FAQ is an interesting read that explains many more details about the app. Credit: Pexels Delta Chat is unique among messaging apps because it is built on email, a technology that’s decades old and isn’t going anywhere soon. What’s more is that email is not centralized either, so it’s far more difficult for any authoritarian regime to disrupt the Delta Chat app. I haven’t spoken too much about features yet, so I will do that now. Delta Chat allows you to do one-on-one chats, group chats, and create channels. It also supports file sharing and making audio and video calls when chatting one-to-one, but it’s not available for group chats right now. At the time of writing, the calling functionality is disabled and can be enabled in Settings > Advanced > Debug Calls. I have used the video calling feature, and the quality is excellent. It works over WebRTC, another open standard. The app also lets you send voice notes, enables disappearing messages, and has its own app ecosystem. I did try playing chess one time there, but it was a bit spotty; though, we did manage to complete the game with a victory for me. To add people to Delta Chat, you can either give them your Delta Chat link or your QR code to scan. These are the only ways to add users, so you won't have any spam bots bothering you. If the people you want to chat with don't have the app yet, just send them your link, and it will take them to a webpage where they can install the app and then add you. It's really quick for them to install it and get started, which is nice. Credit: Microsoft. The Majorana 2 quantum chip unveiled in 2026. I do not think quantum computers are too far out now, and I do hope that Delta Chat is able to push out Autocrypt v2 sooner, rather than later, so bad actors do not attempt to collect encrypted communications and then decrypt them in the future using quantum computers. By getting people’s messages post-quantum-safe now, users won’t have to worry when quantum computers start cracking legacy encryption. Overall, I would recommend this app to people who are already past WhatsApp and Messenger and have perhaps begun using apps like Telegram or Session. It shares a lot of characteristics with these apps and goes a lot further than Telegram in terms of security. By being based on email, it is also resistant to censorship, and the lack of a username and password makes you anonymous (if you want to be) and safe from brute force password cracking attempts. Let me know in the comments if you’ve tried Delta Chat recently. Do you think it's a good bulwark against governments that are tightening their grip on the internet?
  • Recent Achievements

    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      474
    2. 2
      +Edouard
      220
    3. 3
      PsYcHoKiLLa
      156
    4. 4
      Steven P.
      73
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!